You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
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 runsource 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
The text was updated successfully, but these errors were encountered: