this post was submitted on 30 Mar 2025
173 points (100.0% liked)

Selfhosted

45393 readers
883 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

What's up, what's down and what are you not sure about?

Let us know what you set up lately, what kind of problems you currently think about or are running into, what new device you added to your homelab or what interesting service or article you found.

you are viewing a single comment's thread
view the rest of the comments
[–] TK420@lemmy.world 5 points 3 days ago (1 children)

Docker compose. I had a plan to ease into docker, I slipped and fell in the fucking pool. So far I have AdGuard Home and Heimdall working. Some WireGuard variant is next, followed by moving grafana and Prometheus over.

So far so good…..internet blogs, videos, etc have been not great, seems things have changed since dropping the version in your yaml file. All in all, I think the direction I’m heading in is good. Time will tell.

[–] sugar_in_your_tea@sh.itjust.works 5 points 3 days ago (1 children)

Docker compose is great! Good luck!

I've been moving from docker compose to podman, and I think that's the better long term plan for me. However, the wins here are pretty marginal, so I don't recommend it unless you want those marginal wins and everything is already in containers. IMO: Podman > docker compose >>>no containers. Docker compose has way better examples online, so stick with that until you feel like tinkering.

[–] TK420@lemmy.world 3 points 3 days ago (1 children)

I really like the idea of containers, it def solves my problems of running multiple services in the host OS. I’d like to build my own containers to pull the few “bare metal” services I’ll have outside of docker. Anyway, I’ll keep podman in the back of my head.

One thing I’m already happy I did was create a docker directory and having sub directories keep all of my container volumes separate. Should make backing things up easier as well.

Yeah, containers are great! It's really nice knowing exactly which directories to move if I need to rebalance my services onto other hardware or something.

Most of my services are on my NAS, so I have this setup:

  • /srv/nas/ - everything here is on my RAID, and offsite backups look here (and exclude certain directories to save on cost
  • /home//containers - my git repo with configs, sans passwords/keys
  • configs w/keys live in my password manager

Disaster recovery should be as simple as:

  1. Copy my data from backup into /srv/nas
  2. Clone my container repo
  3. Copy env files to their respective locations
  4. Run a script to get things set up

I use specific container versions, so I should get exactly the same setup.

I'm going to be reinstalling my NAS soon (boot drive is getting old), so we'll see how this process works, though I'll skip step 1 since I'm keeping the drives.