Backups are encrypted so it shouldn’t be an issue.
Comment on Backup compose and env files
PunkRockSportsFan@fanaticus.social 4 weeks ago
Keeping backup of .env means exposing sensitive creds ?
MangoPenguin@lemmy.blahaj.zone 4 weeks ago
HelloRoot@lemy.lol 4 weeks ago
what about a local, encrypted backup
PunkRockSportsFan@fanaticus.social 4 weeks ago
It’s like you have secrets that you pull in to build your .env which should only be used by the stuff that needs it and it’s not shared.
I’m assuming this is a production backup and the idea that someone has a prod .env file gives me the Willies.
Id want to change all the cards.
grimer@lemmy.world 4 weeks ago
In my particular case I only have a few .env files and they don’t have any credentials in them. This is mostly for the docker-compose files.
shadybraden@programming.dev 4 weeks ago
You can specify a folder in your files for configs, and a different one for the compose and env: