Variable in multiple .env files not supported

[trek]

I'm a bit confused about the exact timing and provenance of this but:

The guides say "Variables defined in an deploy-target specific file will override those defined in a top-level .env file."

There's even a code comment about ordering being important here.

But the dotenv project contradicts this "We will never modify any environment variables that have already been set. In particular, if there is a variable in your .env file which collides with one that already exists in your environment, then that variable will be skipped."

I'm seeing the behavior described in the dotenv README, but would love someone to verify. If it's actually been removed I'd be happy to PR either their example work-around (that they suggest avoiding) or PR removing this from the guides.

[ghedamat]

Hey @trek

It's been a while since I last touched this but,
this should be the correct order of precedence

• first your ENV already has the variable (i.e. by setting it inline MYVAR=foo ember deploy production)
• second you have a .env.deploy.production env available (if you're deploying to the production deployTarget)
• third you have a .env file in your project

in this order the variables will be loaded and will not be overridden if one of the previous steps on the list has already defined them

I do agree that the documentation around this should be better

Let me know if this helps!