Skip to content
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

Should env defined variables override .env? #85

Closed
nvartolomei opened this issue Jun 9, 2016 · 2 comments
Closed

Should env defined variables override .env? #85

nvartolomei opened this issue Jun 9, 2016 · 2 comments

Comments

@nvartolomei
Copy link

This is what I expected actually.

@ddollar
Copy link
Owner

ddollar commented Jun 18, 2016

I think this could easily lead to unexpected scenarios. Could you provide an example of this please?

@tomeon
Copy link

tomeon commented Feb 28, 2017

Although this issue is closed, it's perhaps worth mentioning that what the OP expects is dotenv's default behavior, justified on the assumption that

the deployment environment has more knowledge about configuration than the application does.

Maybe this behavior could be optional -- say, via a flag like --preserve-env? I would be happy to submit a PR adding this feature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants