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!

  • grimer@lemmy.worldOPEnglish
    1·
    3 days ago

    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!

    • shadybraden@programming.devEnglish
      41·
      3 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