It should be fine, unless you're using encrypted fields, using the SECRET_KEY setting as the key, and have a different key in production.
Of course, if you want to keep the databases in sync after that, that's another issue. On Apr 8, 2013 5:09 PM, "Tim Johnson" <[email protected]> wrote: > FYI - I'm new to django, but have been doing web programming since > '96 and python since '03. > > I intend to put together a test site on my desktop and push it to a > remote server. I will be the only user making changes to this site. > > Thus I presume that it is OK to push the database as well. > > Am I correct? > > And URLs to discussion and instructions on deployment are invited. > :) > > thanks > -- > Tim > tim at tee jay forty nine dot com or akwebsoft dot com > http://www.akwebsoft.com > > -- > 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 [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/django-users?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
