Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
dotenv override?
See original GitHub issueIs there any reason override is set to True here? dotenv.load_dotenv(denv, override=True)
I prefer using envdir since it lets me explicitly define the environment variables for local development vs production. I end up creating a .env file anyway for compatibility with other software like pipenv, docker-compose, pycharm, etc.
When I want to run my app locally using production environment variables, I’m running into an issue because of the override=True.
The command envdir envs/prod pipenv run python src/manage.py runserver will end up using the .env variables instead of those provided through envdir.
Can you either set override to False or allow disabling .env files?
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
added a patch
I’ll give it a shot. It feels weird to create an env file just to run my app in a different way. I really like what pipenv and pew do with subshells and I think envdir just takes that a step forward.
I do think this the configuration should exist though if pipenv wants to be / is the “official” language package manager which tend to be less opinionated and more unix-y (less features, more configurable and composable with other tools).