this post was submitted on 21 Sep 2025
103 points (100.0% liked)

Selfhosted

60366 readers
689 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
ayyy@sh.itjust.works
curbstickle@anarchist.nexus
curbstickle_lw@lemmy.world
103
Selfhosting Sunday! What's up? (lemmy.nocturnal.garden)
submitted 9 months ago by tofu@lemmy.nocturnal.garden to c/selfhosted@lemmy.world
98 comments fedilink hide all child comments
 

With the recent discussions around replacing Spotify with selfhosted services and the possibilities to obtain the music itself, I've been finally setting up Navidrome. I had to do quite a bit of reorganization to do with my existing collection (beets helping a ton) but now it's in a neatly organized structure and I'm enjoying it everywhere. I get most of my stuff from Bandcamp but I have a big catalog from when I've still had a large physical collection.

I'm also still working on my docker quasi gitops stack. I've cleaned up my compose files and put the secrets in env files where I hadn't already, checked them into my new forgejo instance and (mostly) configured renovate. Komodo is about to get productive but I couldn't find the time yet. Also I need to figure out how to check in secrets in a secure way. I know some but I haven't tried those with Komodo yet. This close of my fully automated update-on-merge compose stacks!

I've also been doing these for quite a while and decided to sometimes post them in !selfhosting@slrpnk.net to possibly help moving a bit from the biggest Lemmy instance, even though this community as it is is perfectly fine as well as it seems.

What's going on on your servers? Anything you are trying to pursue at the moment?

you are viewing a single comment's thread
view the rest of the comments
[–] greybeard@feddit.online 16 points 9 months ago (3 children)

I spent some time last week learning both Ansible and Podman Quadlets. They are a powerful duo, especially for self hosting.

Ansible is a desired state system for Linux. Letting you define a list of servers and what their configuration should be, like "have podman installed" and "have this file at this location with this content".

Podman quadlets is a system for defining podman containers as a service. You define the container, volumes, and networks all in essentially Systemd unit files.

Mixing the two together, I can have my entire podman setup in a format that can be pushed to any server in seconds.

And of course everything is text files that git well.

[–] theorangeninja@sopuli.xyz 3 points 9 months ago (1 children)

I was thinking about this for some time now, can you link me to some good tutorials about quadlets in particular? Ansible will have to wait for now.

[–] greybeard@feddit.online 2 points 9 months ago (1 children)

Unfortunately not. I found documentation largely lacking. I mostly read the docs and searched specific questions that came up(which often just took me back to the docs). I did as a local LLM for help, but found it's knowledge base lacking. Sometimes it would work for a hint, but it more often than not made up parameters and features.

[–] theorangeninja@sopuli.xyz 1 points 9 months ago (1 children)

Which docs did you read in particular? If you mind to share? And so nice, that you setup a local LLM. I sadly don't have the horsepower for that.

[–] shadowtofu@discuss.tchncs.de 3 points 9 months ago (1 children)

I did the same last week (and am still in the process of setting up more services for my new server). I have a few VMs (running Fedora CoreOS, with podman preinstalled), and I use ansible to push my quadlets, podman secrets, and static configuration files. Persistent data volumes get mounted using virtiofs from the host system, and the VMs are not supposed to contain any state themselves. The VMs are also provisioned using using ansible.

Do you use ansible to automatically restart changed containers after pushing your changes? So far, I just trigger a systemctl daemon-reload, but trigger restarts manually (which I guess is fine for development).

[–] greybeard@feddit.online 2 points 9 months ago

I haven't gotten too far, but right now I've got persistent volumes being pushed by NFS from my NAS. I'm using rocky Linux VMs as my target, but for this use case, Fedora CoreOS should be the same.

I haven't yet tried using Ansible to create the VMs, but that would be cool. I know teraform is designed for that sort of thing, but if Ansible can do it, all the better. I'd love to get to a point where my entire stack as Ansible.

I don't yet have Ansible restarting the service, but that should be a simple as adding a few new tasks after the daemon-reload task. What I don't know how to do is tell it to only restart if there is change to any of the config files uploaded. That would be nice to minimize service restarts.

[–] powerofm@lemmy.ca 2 points 9 months ago

Oh that's smart! I just got started with podman and quadlets. Loving how simple it is to setup a systemd service and even organize multi-pod apps