Allow destination specific envifying

This commit is contained in:
David Heinemeier Hansson
2023-02-05 16:35:37 +01:00
parent e865e823d5
commit 02a5726072
2 changed files with 8 additions and 2 deletions

View File

@@ -329,6 +329,8 @@ MYSQL_ROOT_PASSWORD=<%= `op read "op://Vault/My App/MYSQL_ROOT_PASSWORD" -n --se
This template can safely be checked into git. Then everyone deploying the app can run `mrsk envify` when they setup the app for the first time or passwords change to get the correct `.env` file.
If you need separate env variables for different destinations, you can set them with `.env.destination.erb` for the template, which will generate `.env.staging` when run with `mrsk envify -d staging`.
## Commands
### Running commands on servers