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.
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.