By the way, the docs for SECRET_KEY have a description of what will be invalidated if you change it:
https://docs.djangoproject.com/en/stable/ref/settings/#secret-key On Wednesday, August 5, 2015 at 11:16:21 AM UTC-4, Simon Charette wrote: > > Hi Angit, > > It shouldn't be an issue since Django's default password hashers are not > relying on settings.SECRET_KEY. > > Simon > > Le mercredi 5 août 2015 05:12:47 UTC-4, Ankit Agrawal a écrit : >> >> >> >> Hi everyone, >> >> >> I have a Django powered site(Project-1) running with some users >> registered on it. I am now creating a revamped version of the site in a new >> separate Django project(Project-2) which I would make live once finished. I >> would need to populate the User data along with their hashed passwords >> currently in database of Project-1 into database of Project-2. Would having >> different SECRET_KEYs for Project-1 and Project-2 be an issue to get the >> hashed passwords migrated and working in Project-2? >> > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/f611620c-ad66-482a-b999-67f17b94886f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
