Tuesday, December 1, 2015

Transitioning existing login portal to Django

Hello,

Does anyone have experience with transitioning an existing database including user login data to Django?

I am about to begin work on a startup's hand-written web portal that consists of about 2000 lines of custom Python code (hashing passwords, managing user accounts, DB connections, etc.), some Mako templates, and a Postgresql database. A hand-written web framework makes me nervous for many reasons. I don't have access to the source code or the database yet, but my plan is to transition it to Django 1.8. I'd like to use inspectdb to help generate the models, but I doubt inspectdb will be smart enough to handle usernames and password hashes properly. How can I make sure this data gets transferred correctly?

I'm looking for ideas about how to proceed and/or what to expect during the transition. Thanks.

-EP

--
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+unsubscribe@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/5fc8e870-68ef-4012-91e5-2467c7d0394f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment