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

Install python decouple to improve working environment variables in virtual environment #713

Closed
dakaza98 opened this issue Feb 8, 2023 · 1 comment · Fixed by #715
Closed
Assignees

Comments

@dakaza98
Copy link
Member

dakaza98 commented Feb 8, 2023

Both Bocken and OrdSys use a tool called python-decouple for handling environment variables. It's main benefit over the current solution is that the environment variables (.env-normal file) is only loaded when you run source source_me.sh. This means that if you were to change one of the environment variables you would have to run source source_me.sh again which is not intuitive (this has caused errors before). With Python decouple, the environment files are loaded each time the server is started which is much easier to work with.

It will however require some changes to the .env-normal file of anyone who is working on project moore but its a very simple fix

@dakaza98 dakaza98 self-assigned this Feb 8, 2023
@dakaza98
Copy link
Member Author

dakaza98 commented Feb 8, 2023

This would also harmonize the env files since the .env file could then be used by both docker and virtual environment. Currently they have to be separated since .env-normal uses export commands. I.e. we could just have one .env-template that you copy and make into .env

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 a pull request may close this issue.

1 participant