#31757: Adjust default SECRET_KEY to use `dj::insecure` prefix and add matching
deployment system check.
------------------------------------------------+------------------------
Reporter: Carlton Gibson | Owner: nobody
Type: New feature | Status: new
Component: Core (System checks) | Version: 3.0
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------------+------------------------
[https://groups.google.com/d/topic/django-
developers/CIPgeTetYpk/discussion Recent thread on the mailing list about
making the default settings more 12 factor friendly]. (Related to similar
discussions in say #20081.)
Conclusion there was that environment variables are only one way to go.
(...)
In the discussion it came up that we could prefix the generated SECRET_KEY
with say, `dj::insecure` and then add a deployment system check to ensure
that wasn't used in production. (Paraphrasing various points: might not be
100% robust but would capture most cases.)
So:
* Prefix secret key in project template.
* Add system check to ensure secret key does not have prefix.
--
Ticket URL: <https://code.djangoproject.com/ticket/31757>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/056.097fcd49381c7a656d01fda837dc522f%40djangoproject.com.
