-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Security hardening on deployment (e.g. SECRET_KEY ends up on GitHub) #1192
Comments
IMHO it's already hard enough so we shouldn't requiring to do this manually. #1190 would be a good starting place. |
Agree, and #1190 is indeed a better option. But if security would be a topic at some point these steps aren't that hard. |
I see this issue is a generalized copy of #802. |
3 tasks
closing in favour of DjangoGirls/tutorial-extensions#101 |
Related: #1687 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue description
I will soon be coaching the tutorial, and went through it myself to get to know it. I noticed that with the current steps there are some security issues like the SECRET_KEY ending up on GitHub.
Given the current importance of security it would be nice to have a section on these hardening steps. This can include:
The text was updated successfully, but these errors were encountered: