Ok, so reading the replies I see that it was meant for me.
All the relevant volumes are mapped to the actual filesystem on disk (like you do in docker compose, ig it’s called a volume bind-mount?), so when I have to take backups I stop the docker container and manually cp/rsync/whatever from the directory.
The github and codeberg services are nothing but HTTPS checks for both of them
carlnewton@feddit.uk 3 weeks ago
I keep my container volumes in sub-directory of that of the docker compose file and tar them up and put them somewhere safe. I spent ages trying to figure out how to back up a container, because I thought that the state of a database was in memory, which I suppose it is, but when you stop it, it’s just a bunch of files like everything else, so I elected to keep it simple. I’ve been thinking of creating a cron job to do it routinely. I’m not sure what you mean regarding the codeberg question.
kalapala@sopuli.xyz 2 weeks ago
Picture has title services and under it there’s Codeberg and GitHub. Is it just the state of the public service or do you have some repos monitored there or something? I just wonder why are those there as you probably have no source for… Okay well maybe you could have codeberg source code but GitHub?
carlnewton@feddit.uk 2 weeks ago
Oh I see! I’m not the OP. I’m not sure if you meant to respond to my comment initially.
kalapala@sopuli.xyz 2 weeks ago
Oh no I did this again. Thanks for pointing out.