Comment

Comment on Backup compose and env files

RegalPotoo@lemmy.world ⁨1⁩ ⁨week⁩ ago

Check them into Git, but be cautious about credentials that might live in the env files that you don’t want to expose publicly.

Sort:hotnew top

grimer@lemmy.world ⁨1⁩ ⁨week⁩ 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!

source
- shadybraden@programming.dev ⁨1⁩ ⁨week⁩ 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
  
  source