Django docs state the flush command installs any initial data - in
Mezzanine that equates to a few demo pages and default user account.
https://docs.djangoproject.com/en/1.8/ref/django-admin/#flush
There's no development to production migration of data occurring. The
only correlation with the twitter app is that there is no initial data to
install.
On Sat, May 16, 2015 at 9:27 AM, Graham Oliver greenbay.gra...@gmail.com
wrote:
Hello all
I am just working through the process of moving data from development to
production (which I will document at some point)
I notice that after I do a 'flush' command various bits of data spring
back to life. Doing some research I see that this is because of something
called a post_migrate signal...
I have a few questions
1. Is there a reason why the twitter model is the only model in Mezzanine
to be affected by this?
2. Can you point me to the lines of code where this happens (the
post_migrate actions for the twitter model)
3. When I run the 'flush' command with verbosity 3, I see this comment
'[108.59.11.112] out: Creating example.com Site object'. Would it be a
good idea to have something similar for the twitter objects that are
created?
TIA
Graham
--
You received this message because you are subscribed to the Google Groups
Mezzanine Users group.
To unsubscribe from this group and stop receiving emails from it, send an
email to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Stephen McDonald
http://jupo.org
--
You received this message because you are subscribed to the Google Groups
Mezzanine Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
