#20181: auto generate SECRET_KEY file?
-------------------------------------+-------------------------------------
Reporter: michael.vogt@… | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: 1.5
Component: Uncategorized | Resolution:
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by pegler):
This idea was suggested on the django-developers mailing list a while ago
(https://groups.google.com/forum/?fromgroups=#!searchin/django-
developers/secret$20key$20from$20file/django-
developers/KKoCec5j9mg/Kf4-_Mr07EwJ). From the discussion in that thread,
it seems that the preferred method is to use multiple settings files where
you store general settings in a settings_global.py file and then keep
settings.py out of version control and have it do something like
{{{
from settings_global import *
SECRET_KEY = '.....'
}}}
I personally think that's a better approach since you're going to be
overriding many settings for your various environments
(dev/stage/test/prod) and not just the secret key. But I'll leave this
open for others to weigh in.
Best,
Matt
--
Ticket URL: <https://code.djangoproject.com/ticket/20181#comment:2>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
