this post was submitted on 20 Aug 2024
47 points (94.3% liked)

Selfhosted

39251 readers
267 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 1 year ago
MODERATORS
 

Question.

you are viewing a single comment's thread
view the rest of the comments
[–] drkt@lemmy.dbzer0.com 23 points 4 weeks ago (1 children)

By having it be a container

[–] TheBigBrother@lemmy.world 3 points 4 weeks ago (2 children)
[–] lemmyng@lemmy.ca 18 points 4 weeks ago (1 children)

The container is reproducible. Container configuration is in version control. That leaves you with the volumes mounted into the container, which you back up like any other disk.

[–] pixxelkick@lemmy.world 15 points 4 weeks ago* (last edited 4 weeks ago)

Dunno why ppl are down voting you, this is 100% the way.

Architecture as code is amazing, being able to completely wipe your server, re-install fresh, and turn it on and it goes right back to how it was is awesome.

GitOps version controlled architecture is easy to maintain, easy to rollback, and easy to modify.

I use k8s for my entire homelab, it has some initial learning curve but once you "get it" and have working configs on github, it becomes so trivial to add more stuff to it, scale it up, etc.

[–] drkt@lemmy.dbzer0.com 3 points 4 weeks ago

All of my services run on LXC containers. Some files and configs are backed up to NAS and offsite. The containers are snapshotted in their entirety before I do any work on them. A snapshot takes 5 seconds to make and causes no downtime. If I regret a change or mess it up, I can restore the snapshot in under a minute at the cost of some seconds of downtime.

My only non-container machines are my desktop (doesn't count), my NAS and the Hypervisor. The Hypervisor is very clean and wouldn't be much fuss to reinstall and the NAS is literally just Debian with NFS. All of these have a regular rsync which runs to backup the important files.