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
classy-start project <project-name> already creates a .env file. But this file's pattern has been rightfully added to .gitignore and probably never leaves the developer's PC.
It would be nice to have a .env.example which starts out containing the variables in the .env file, but without their values. For now its content could be:
SECRET_KEY = ""
DEBUG = True
# space delimited string of allowed hosts
ALLOWED_HOSTS = ""
This one will at least get sent to remote on push, so other developers can have an idea what environment variables they are to set for the project to work well.
Working on this issue, you'll only have to update the following function:
classy-start project <project-name>
already creates a.env
file. But this file's pattern has been rightfully added to.gitignore
and probably never leaves the developer's PC.It would be nice to have a
.env.example
which starts out containing the variables in the.env
file, but without their values. For now its content could be:This one will at least get sent to remote on push, so other developers can have an idea what environment variables they are to set for the project to work well.
Working on this issue, you'll only have to update the following function:
django-classy-start/classy_start/start.py
Lines 43 to 59 in fbf0500
And its associated test function:
django-classy-start/tests/test_start.py
Lines 55 to 100 in fbf0500
The text was updated successfully, but these errors were encountered: