Use South for schema migrations
We should implement South in our workflow.
I mistakenly thought that Django 1.6 supported migrations native, but that's not untill 1.7.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Medium
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- Mathias Bøhn Grytemark
- Definition:
- Approved
- Series goal:
- Accepted for lancms2
- Implementation:
-
Informational
- Milestone target:
- None
- Started by
- Mathias Bøhn Grytemark
- Completed by
- Mathias Bøhn Grytemark
Related branches
Related bugs
Sprints
Whiteboard
Added south in requirements and settings.
I've configured south to ignore all apps except (currently) 'core'. I've hit some error that seems to be a bug in south 0.8.3 (I'm running 0.8.4 and it should be fixed) with AUTH_USER_MODEL. It works for 'core' at least so I think we're okay untill we have time to/need to look at it again. :-)
When setting up a new install we need to run './manage.py migrate core' after we've done the normal './manage.py syncdb'. ('core' and eventually other apps is listed in 'syncdb' as "Not synced (use migrations)".)
http://
Work Items
Dependency tree
* Blueprints in grey have been implemented.
