21.2.2013 18:02, Santiago Basulto kirjoitti:
Hello guys,
we've our app that's working awesome. We do a new release each week.
We've set up a nice deployment process using fabric and everything
works great.
The problem is that, as the application grows, it takes some time to
perform the deploy. And we're using South, so sometimes we need to
migrate some big tables.
So, the questions are:
* How should I lock my DB in the moment of the deployment? Should I
use different DB users at that moment?
* What other strategies do you use at the moment of the deployment you
can recommend?
Thank you very much!
You can't "lock" your database in that sense.
Simplest thing and what you usually do is to just bloock all unwanted
access to your database like shutdown all running deployments for a
upgrade period.
For downtime period you can setup static page to state that "maintenance
in progress" or some other meanful information.
--
Jani Tiainen
- Well planned is half done and a half done has been sufficient before...
--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
