Repository navigation
Remove hardcoded Django SECRET_KEY value - #167
Merged
Merged
Conversation
Even though SECRET_KEY isn't actually used by this project (there's no Django auth, no admin, no sessions, no encrypted data), Django still requires a value be set. We shouldn't be hardcoding in in the settings file like this, though. Default to a random value, or provide one via the DJANGO_SECRET_KEY environment variable.
wpears
approved these changes
Oct 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Even though SECRET_KEY isn't actually used by this project (there's no Django auth, no admin, no sessions, no encrypted data), Django still requires a value be set. We shouldn't be hardcoding in in the settings file like this, though. Default to a random value, or provide one via the DJANGO_SECRET_KEY environment variable.