Selfhosted

45411 readers

312 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 2 years ago

MODERATORS

[email protected]

Backup compose and env files (lemmy.world)

submitted 4 days ago* (last edited 1 day ago) by [email protected] to c/[email protected]

13 comments fedilink hide all child comments

Just curious if there is an easy way to back up my docker-compose.yaml and .env files. I have the following directory structure for my containers:

-docker
  -<name of container>
    -.env
    -docker-compose.yml

I'd like to copy those two files for each container folder but no other subfolders that may also be in the container folder (config, data, etc). I've been trying to get my restic backups to do it but I just can't figure it out.

Is there a better way? I'd like to have backups in case my entire server dies.

UPDATE: Thank you all for the advice, I'm giving git a try and so far so good!

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 12 points 4 days ago* (last edited 4 days ago) (1 children)

Check them into Git, but be cautious about credentials that might live in the env files that you don't want to expose if you end up making the repo publicly available.

[–] [email protected] 1 points 4 days ago (1 children)

That is an option I've been thinking about but I've never used it, I'm not a dev. Maybe I'll look at it more seriously since it does sound like what would work best, I'd really apprecieate the versioning. Thanks!

[–] [email protected] 3 points 4 days ago

Definitely worth a shot.

One thing I do to prevent stuff from getting into a public git repo is:

In the git repo, make a file called .gitignore then add the line .env to it. Then git will ignore any file named .env
edit compose files from a computer that is separate from the one that gets secrets. I have my desktop setup to push to github. Then I make a change, then simply run `git pull on my server to download the changes.
make the .env only viewable by root (you'll have to use sudo nano) by running sudo chmod 600 .env && sudo chown root:root .env