Deploying Django multi servers, 1 DB server

[Peter van der Does]

We currently have one app server, so deployment with migrations is easy, but we're expanding to multiple app servers and one DB server.

How do people handle migrations? I understand you run migrations on one server only. But how do you inform the other servers that migrations has finished and they can start doing the next steps.

We're open to using any DevOps tool, Ansible, Puppet, Chef.
We don't do any form of CI, nor are we planning to do so in the near future.

If more details are needed let me know and I can provide them.

--

Peter van der Does
o: 410-584-2500

m: 732-425-3102

ONeil Interactive, Inc 

oneilinteractive.com

[Christian Ledermann]

You will have to split migrations from code changes.

The migrated database will have to run with both old and new code.

You may have to split one migration into several to achieve this

--
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...@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/8a49a438-eb2f-78ab-bc5a-ae9edb1a07af%40oneilinteractive.com.
For more options, visit https://groups.google.com/d/optout.

--

Best Regards,

Christian Ledermann

Newark-on-Trent - UK
Mobile : +44 7474997517

https://uk.linkedin.com/in/christianledermann
https://github.com/cleder/


<*)))>{

If you save the living environment, the biodiversity that we have left,
you will also automatically save the physical environment, too. But If
you only save the physical environment, you will ultimately lose both.

1) Don’t drive species to extinction

2) Don’t destroy a habitat that species rely on.

3) Don’t change the climate in ways that will result in the above.

}<(((*>