how do you guys handle env vars per environment (dev, staging, production)? I can only think of two ways - pass them manually when running

graphcool deploy

or a shells script per environment e.g

./deploy-prd.sh

I personally use env files containing my exports and source them on the terminal before using

gc deploy

great idea with the colors 👍

nice, thanks @florian

One last thing I can share, I managed my env files in git, here is my env folder locally:

env/
├── .envrc.dev #.gitignored
├── .envrc.dev.secret
├── .envrc.prod #.gitignored
├── .envrc.prod.secret
├── .envrc.staging #.gitignored
└── .envrc.staging.secret

Only the .secret files are commited (others are ignored). The secret files are encoded with gnupg which allows acl to each files (All developers have access to the dev file, only the Lead dev and I have access to the staging and prod ones)

thats perfect, thanks.

We’re using Torus - https://www.torus.sh/

check this discussion, too https://www.graph.cool/forum/t/assign-different-values-to-an-env-var-for-each-target/1224?u=nilan

awesome, thanks guys