Changing SECRET_KEY for a project that was already launched

[cool-RR]

Hi guys,

I have a project online whose SECRET_KEY was compromised. I obviously want to change it. Would anything bad happen if I change it? Would some things not work? Is it safe to just change it? Anything I should do?

Thanks,

Ram.

[Shawn Milochik]

Are you using it as the key for any encrypted fields, or anything
other than the built-in stuff Django does with session cookies?

If not, I don't think you'll have a problem. Of course, back up your
database first as a precaution, and use version control on your code
so you can revert if necessary.

[Ram Rachum]

Thanks!

--
You received this message because you are subscribed to a topic in the Google Groups "Django users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/django-users/X-urJnLjzTY/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to django-users...@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.