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

Added functionality for setting multiple paths. #259

Closed
wants to merge 2 commits into from
Closed

Added functionality for setting multiple paths. #259

wants to merge 2 commits into from

Conversation

mkovel
Copy link

@mkovel mkovel commented Jan 28, 2018

No description provided.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling c64fd72 on mkovel:multiple_path into 6b07ace on motdotla:master.

2 similar comments
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling c64fd72 on mkovel:multiple_path into 6b07ace on motdotla:master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling c64fd72 on mkovel:multiple_path into 6b07ace on motdotla:master.

@maxbeatty
Copy link
Contributor

This is in conflict with our guidance that you should only have a single .env file. If you must use multiple paths, you can handle this yourself

const dotenv = require("dotenv")

['.env', '/custom/path/to/your/env/vars'].forEach(path => dotenv.config({ path }))

@maxbeatty maxbeatty closed this Jan 29, 2018
@mkovel
Copy link
Author

mkovel commented Feb 1, 2018

@maxbeatty Hi, let me describe the main idea.
My change still has the one .env file, but it can place in different places.
I stop processing after than I found the first file.
It is not the same that you provided above.

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

Successfully merging this pull request may close these issues.

3 participants