Can't generate SECRET_KEY.
See original GitHub issueIn CONTRIBUTING.md
it says to generate the SECRET_KEY from the django shell, but in fact, you can’t run the shell itself unless your SECRET_KEY is set-up.
That’s why I suggest to remove the environment variable and put a SECRET_KEY generated prior so that people can generate it on their machine and then use the python-dotenv
library to keep their virtual environment variables in a .env
file.
Edit:
Also, set Debug
to True
since it’s the development code.
Edit 2:
README.md/CONTRIBUTING.md
might have to be updated accordingly.
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Secret key can not be omitted · Issue #1936 · argoproj/argo-cd
So the server.secretkey has to have a unique value and should be generated on its own. We cannot assign a value of our...
Read more >Generate Secret Key - Okta Support
Hi Everyone, I have a question - whether Okta administrator can generate secret key for Okta Verify for a normal user?
Read more >android - Get the SecretKey value generated by KeyGenerator ...
Problem : I am unable to get the string/bytes value of the SecretKey which I want to encrypt.
Read more >SonarQube DE Container - Unable to Encrypt Values (cannot ...
I do the following: generate the secret key; save the key to /root/.sonar/sonar-secret.txt on the container; change file ownership to ...
Read more >Find your Secret Key or Setup Code - 1Password Support
You can find your Secret Key and Setup Code in the 1Password app on any device where you're already signed in to your...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Maybe move some stuff from
CONTRIBUTING
toREADME
? I feel as if a lot ofREADME
worthy stuff is inCONTRIBUTING
. I suggest moving “About the Project” and “Getting Started” to the README and we can put the “Installation” heading in theREADME
under “Getting Started” heading.How about this for “Getting Started”?:
Separate points 6 through 9 in the
CONTRIBUTING
section.Shall I get started?
settings.py
will need to be updated as well. Need to comment out theSECRET_KEY
andLOCAL_HOST
variables. Then mention uncommenting those out in theREADME
as well.