This repository has been archived by the owner on May 3, 2022. It is now read-only.
Place SECRET_KEY in dev.py and local.py only #8
Conversation
This file contains 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
kaedroho
added a commit
that referenced
this pull request
Sep 16, 2014
Place SECRET_KEY in dev.py and local.py only
|
Thanks! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
While fiddling with settings files I noticed it might make sense to enforce setting
SECRET_KEYand other confidential data indev.pyandlocal.pybut not inbase.py.This will make sure:
dev.pybase.pynor inproduction.py) but instead set in itslocal.pyDoes this make sense at all?