On Thu, Jun 20, 2013 at 4:29 PM, Michael Cetrulo wrote:
> considering that the SECRET_KEY is automatically generated every time a new
> project is created [1], wouldn't make more sense to have this logic on
> settings.py and generate a new value when loading the app instead of saving
> it as an ac
considering that the SECRET_KEY is automatically generated every time a new
project is created [1], wouldn't make more sense to have this logic on
settings.py and generate a new value when loading the app instead of saving
it as an actual hardcoded value there? eg:
#settings.py
from django.uti
So the SECRET_KEY is stored in the database at syncdb time? What if it gets
compromised, you need to modify that table/row? Just asking out of
curiosity :-)
2013/6/20 John DeRosa
> When we run the development server locally, we often start with an
> already-existing database. We don't re-initia
When we run the development server locally, we often start with an
already-existing database. We don't re-initialize the db unless we have to,
because there's been a schema change or a change in the value stored in a
table's field.
So we'd need SECRET_KEY to not change most of the time!
John
4 matches
Mail list logo
