Ticket #640 (closed enhancement: fixed)
Documentation suggestion: A way to ignore apps containing migrations
| Reported by: | brian@… | Owned by: | andrew |
|---|---|---|---|
| Priority: | major | Milestone: | 0.7.3 |
| Component: | documentation | Version: | unknown |
| Keywords: | ignore app | Cc: |
Description
Whether or not it may be considered wise to do so, it is likely that a growing number of 3rd party apps will contain South migrations. However it is not always desirable (or even possible if they break) for consumers to maintain the migration lifecycle for 3rd party apps. One alternative is to have South ignore certain apps and manage them with syncdb rather than migrate. This isn't an official feature of South per se, but you can achieve this by using (abusing) the SOUTH_MIGRATION_MODULE setting. The trick is to set the migration to a module that doesn't exist, in which case South assigns the apps for normal syncdb processing:
SOUTH_MIGRATION_MODULES = {'cms': 'ignore',
'text': 'ignore',
'link': 'ignore',
'snippet': 'ignore',
'googlemap': 'ignore',
'filer': 'ignore'}
Since there are no actual modules named ignore in any of those apps, South will effectively manage them with syncdb.

Good suggestion; I've put a small paragraph in [28ec3ce589aa]. Ideally there should be a Common Problems section, but that's more of an overall issue.