Heroku django south doesn't seem to use migrations

Question

I have problems with the migration of the south of Django. This may be due to the way we laid out our project, but it worked earlier, and it works fine on the spot.

I clicked on a new code yesterday containing the migration in my_app application. Therefore, in my local environment ...

 $ ./manage.py migrate --list socialaccount (*) 0001_initial (*) 0002_genericmodels (*) 0003_auto__add_unique_socialaccount_uid_provider (*) 0004_add_sites (*) 0005_set_sites (*) 0006_auto__del_field_socialapp_site (*) 0007_auto__add_field_socialapp_client_id (*) 0008_client_id (*) 0009_auto__add_field_socialtoken_expires_at (*) 0010_auto__chg_field_socialtoken_token (*) 0011_auto__chg_field_socialtoken_token payments (*) 0001_initial users (*) 0001_initial my_app (*) 0001_initial (*) 0002_auto__add_organizerapplication 

In heroku, it does not recognize my_app as an application with migrations. When I try to transfer this application ....

 $ heroku run my_app/manage.py migrate my_app --app=my_app Running my_app/manage.py migrate my_app attached to terminal... up, run.5016 The app 'my_app' does not appear to use migrations. ./manage.py migrate [appname] [migrationname|zero] [--all] [--list] [--skip] [--merge] [--no-initial-data] [--fake] [--db-dry-run] [--database=dbalias] 

If I list the migration, you will notice that my_app is not specified ...

 $ heroku run my_app/manage.py migrate --list --app=my_app Running my_app/manage.py migrate --list attached to terminal... up, run.8264 socialaccount (*) 0001_initial (*) 0002_genericmodels (*) 0003_auto__add_unique_socialaccount_uid_provider (*) 0004_add_sites (*) 0005_set_sites (*) 0006_auto__del_field_socialapp_site (*) 0007_auto__add_field_socialapp_client_id (*) 0008_client_id (*) 0009_auto__add_field_socialtoken_expires_at (*) 0010_auto__chg_field_socialtoken_token (*) 0011_auto__chg_field_socialtoken_token payments (*) 0001_initial users (*) 0001_initial 

I'm not sure if this is relevant, but my_app is listed in my INSTALLED_APPS when I check.

UPDATE

The problem was that this particular migration directory __init__.py. missing __init__.py. Executing commands such as convert_to_south via Heroku does not affect this, since local file changes are not saved. When repo returned with this file, migrations were detected. Then I just had to fake the first migration, and I was good.

Answer 1

Make sure you have the init.py file in the transfer folder of the application you want to transfer. The South will work locally, but not in Geroku production. Just copy the init.py file from one of your applications and place it in the migration folder for the application for which you receive an error. Push this change to production, and then migrate.