-
Notifications
You must be signed in to change notification settings - Fork 504
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Loading both .env & .env.* dangerous? #37
Comments
I would highly recommend not pulling production configs locally. In my projects, I consider
|
Make sense thanks, we'll forbid heroku-config usage :) |
Maybe there should be a warning if two env files are being loaded? I had a |
Can you give me more information? It should only load .env and On Saturday, June 1, 2013, Odin Dutton wrote:
|
Any update on this? |
After looking at the code it doesn't seem like it could have ever loaded |
Hi,
I use heroku-config to pull production env variables from Heroku to
.env
locally, so having Dotenv loading both.env
and.env.development|test
can potentially result of having production variable in test env. Not good :)Wouldn't be safer to skip loading
.env
file if a.env.*
file is present?Thoughts?
The text was updated successfully, but these errors were encountered: