If I understand SECRET_KEY right, you'd want to persist it so that login
cookies don't expire every time you restart (or maybe it's worse and per
worker?)
The real trick is that the secret should be the same across all frontend
webapps in a cluster setup
On Dec 26, 2013 11:42 PM, "Jeff Schroeder" <notifications@github.com> wrote:

> In webapp/tests/settings.py:
>
> > @@ -1,3 +1,9 @@
> > +from django.conf import settings, global_settings
> > +
> > +# Silence the warning about an insecure SECRET_KEY
> > +global_settings.SECRET_KEY = 'SUPER_SAFE_TESTING_KEY'
>
> @brutasse <https://github.com/brutasse> Instead, what do you think of an
> approach vaguely like this one<https://github.com/ndarville/pony-forum/blob/master/ponyforum/settings.py#L126>
> ?
>
> Someting kind of like:
>
> >>> ''.join([random.SystemRandom().choice(string.printable) for i in range(100)]).replace(' ', '')
> 'kAgDA\t($ez5ki`YQ<;m^@]p1"4mCwEYC;!_U{[,L\x0c1H.\x0bzEPH7zyWR"\'4BYMtH05u(20G%g`w#qd%s9;;mI.X?a3\r:V!F*2v,xm'
>
> That automatically sets the secret key each time the application is first
> started. Thoughts?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/graphite-project/graphite-web/pull/544/files#r8564053>
> .
>