this post was submitted on 17 Jan 2026
54 points (98.2% liked)

Selfhosted

54644 readers
811 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.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

hi peeps.

Im early on my selfhosting journey and managed to setup some things as a test in docker. the main service im looking to run is ERPNext. after a while I got it up and running so now I want to back this up including all the customization I did in the app.

where to start with this? any intuitive guide?

you are viewing a single comment's thread
view the rest of the comments
[–] fizzle@quokk.au 3 points 14 hours ago (1 children)

My docker files, configs, and volumes are all kept in a structure like:

/srv  
 - /docker  
 - - /syncthing  
 - - - /compose.yml  
 - - - /sync-volume  
 - - /traefik  
 - - - /compose.yml  
 [...]  

I just backup /srv/docker, but I black list some subfolders for things like databases for which regular dumps are created or something. Currently the compressed / deduplicated repos consume ~350GB.

I use borgmatic because you do 1 full backup and thereafter everything is incremental, so minimal bandwidth.

I keep one backup repo on the server itself in /srv/backup - yes this will be prone to failure of that server but it's super handy to be able to restore from a local repo if you just mess up a configuration or version upgrade or something.

I keep two other backup repos in two other physical locations, and one repo air gapped.

For example I rent a server from OVH in a Sydney data centre, there's one repo in /srv/backup on that server, one on OVH's storage service, one kept on my home server, and one on a removable drive I update periodically.

All repo's are encrypted except for the air gapped one. That one has instructions intended for someone to use if I die or am incapacitated. So it has my master password for my password database, ssh keys, everything. We have a physical safe at home so that's where that lives.

[–] mapleseedfall@lemmy.world 1 points 11 hours ago (1 children)

Do you recommend moving an existing volume to this new structure?

[–] fizzle@quokk.au 1 points 8 hours ago

A docker volume?

I only use bind mounts, and in that case you can put them where you like and move them while theyre not mounted by a running container.

Docker volume locations are managed by docker, and i dont use those so not part of the above plan.