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.

Sign up for GitHub

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

Jump to bottom

dotenv_config_path=/custom/path/to/your/env/vars via CLI doesn't work #321

Closed
kodayashi opened this issue Jun 20, 2018 · 4 comments
Closed

dotenv_config_path=/custom/path/to/your/env/vars via CLI doesn't work #321

kodayashi opened this issue Jun 20, 2018 · 4 comments

Comments

@kodayashi
Copy link

Tried preloading dotenv with dotenv_config_path=/absolute/path/to/development.env and the values weren't picked up.

Does this option still work?
@maxbeatty
Copy link
Contributor

It should. Can you provide a failing test case or example project that demonstrates it not working?

@kodayashi
Copy link
Author

Don't have one that I can share ATM, but I was able to work around my issue and don't need this option. When I get some time I can circle back, thanks!

@lewisblackwood
Copy link

lewisblackwood commented Jul 3, 2018 •
edited
Loading

I've noticed this too. I'll try to put together an example project later today.

maxbeatty pushed a commit that referenced this issue Jul 7, 2018
test that dotenv_config_path via cli works ref #321
bfb2269
@maxbeatty maxbeatty mentioned this issue Jul 7, 2018
Merged
2 tasks
@maxbeatty
Copy link
Contributor

just tried to improve the existing test to make sure this is working. please let us know if there's a certain case that is not working

maxbeatty added a commit that referenced this issue Oct 2, 2018
@maxbeatty
Improve CLI option regex (#325)
178e4ba 
* ignore unsupported cli options ref #313

* test that dotenv_config_path via cli works ref #321
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@maxbeatty @kodayashi @lewisblackwood