I am converting an existing codebase (with multiple applications) to use South. Currently, my code base is installed on 1 development server and 3 production servers. The development has its own database, and 3 production servers are connected to one central database.
I read the information at http://south.aeracode.org/docs/convertinganapp.html , but I'm still a little confused about how to proceed.
These are the steps that I plan to follow:
Dev Server: ./manage.py syncdb(To create Southern tables in dev db)
Dev Server: ./manage.py convert_to_south myapp(To create Southern files and records in dev db)
Dev Server: push to VCS
Server 1: pull from VCS(To get South files)
Server 1: ./manage.py syncdb(To create Southern tables in db production)
Server 1: ./manage.py migrate myapp 0001 --fake(To create Southern records in db production)
Server 2: pull from VCS (To get South files)
Server 2: ./manage.py migrate myapp 0001 --fake
Server 3: pull from VCS (To get South files)
Server 3: ./manage.py migrate myapp 0001 --fake
Repeat these steps for all applications.
Question 1:
Is a step required ./manage.py migrate myapp 0001 --fakeon servers 2 and 3? Since I will run migrations on server 1, and all three servers use the same database, it seems that this is not required, but I'm not 100% sure.
Question 2:
If it is required on servers 2 and 3 ./manage.py migrate myapp 0001 --fake, will I need to run a command on servers 2 and 3 every time I transfer the database?
As always, many thanks for your help.
source
share