#20081: Minimize the risk of SECRET_KEY leaks
------------------------------+-------------------------------------
Reporter: Jacob | Owner: aj7may
Type: New feature | Status: closed
Component: Core (Other) | Version: master
Severity: Normal | Resolution: needsinfo
Keywords: nlsprint14 | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* status: assigned => closed
* resolution: => needsinfo
Comment:
So [https://groups.google.com/d/topic/django-
developers/CIPgeTetYpk/discussion the idea of making the settings file
more "12 factor friendly" came up again on the mailing list] — a quite
long thread raising many different points, and approaches.
One key point was, Paul's one from above, that environment variables only
suit a subset of projects. Then there was multiple settings files, and
secrets files, and better deployment docs and...
I have the impression that this ticket was based on a quite specific idea
from a conversion but it's grown quite amorphous, such that I'm not sure
any longer it's actionable. I'm going to close it as needsinfo. Can I ask
that if there's a concrete proposal based on it, that we start a fresh
ticket, perhaps referencing this one if necessary.
Thanks.
--
Ticket URL: <https://code.djangoproject.com/ticket/20081#comment:23>
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/063.ba6fe6311e96e854fb22445f248a6fc4%40djangoproject.com.
