Skip to content

Commit

Permalink
Update migration doc about django migrations errors
Browse files Browse the repository at this point in the history
  • Loading branch information
omab committed Feb 4, 2017
1 parent cd1d086 commit 81c0a54
Showing 1 changed file with 31 additions and 0 deletions.
31 changes: 31 additions & 0 deletions MIGRATING_TO_SOCIAL.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,37 @@ Django users need to add the `social-auth-app-django`
dependency. Those using `mongoengine`, need to add
`social-auth-app-mongoengine`.

### Migrations

Several errors were reported due to migrations not applying properly
when migrating to the new app, most of them are caused because the app
switched names a few times, from `default` to `social_auth`, and
probably something else in between. That's the reason the migrations
define the `replaces` attribute, that way Django can identify already
applied migrations and not run them again.

In order to make complete the move to the new project setup, first
ensure to move to `python-social-auth==0.2.21`, run the migrations at
that point, then continue with the move to the new project and run the
migrations again. Steps:

1. Update to `0.2.21`
```
pip install "python-social-auth==0.2.21"
```

2. Run migrations
```
python manage.py migrate
```

3. Move to the new project

4. Run migrations again
```
python manage.py migrate
```

### Settings

- Update your references to `social.*` in your settings, most notably:
Expand Down

0 comments on commit 81c0a54

Please sign in to comment.