title: Adding South to Django project, development & production
body: <p>Adding South to an existing Django project. I have it installed on both the development machine and the "production" server.</p>
  
  <p>I've done the following on the development machine, then: added South app to settings.py, </p>
  
  <pre><code>python manage.py syncdb
  python manage.py convert_to_south myproject.myapp
  </code></pre>
  
  <p>then changed some models, then</p>
  
  <pre><code>python manage.py schemamigration myproject.myapp --auto
  python manage.py migrate myproject.myapp
  </code></pre>
  
  <p>Seems to work so far. What I am now not so sure about is what to do on the production server. Just repeat all these steps manually? Upload modified settings.py, do syncdb, convert_to_south, upload modified models.py, do schemamigration, migrate? Something different? The tutorial <a href="http://south.aeracode.org/docs/convertinganapp.html" rel="noreferrer">here</a> says something about adding migrations to the version control, so, presumably, they should be uploaded and somehow applied on the production server?</p>
  
  <p>Furthermore, right now I am using sqlite3 on the development machine and mysql on the server - does it make things any different south-wise?</p>