When working on a site, now a new requirement is included, support for multiple sites. This is Ok, django.contrib.sites is fine and DjangoSEO supports this via the Metadata.Meta.use_sites attribute. But if the site is initially deployed with Metadata.Meta.use_sites = False, when setting this to True of course there's a missing column _site_id.
Of course, quickly South comes to my mind, but there's a problem: DjangoSEO is not using migration, and migrations are stored in the app directory, so it would be tinkering with a package inside the site-packages directory.
However I can think on associate the Metadata models with the apps that contains the seo.py module, since the models are being created dynamically, and then the migrations would be inside the VCS tracked app. The developer can change settings, inspect changes with South, generate an apply migrations, all under his app scope.
When working on a site, now a new requirement is included, support for multiple sites. This is Ok,
django.contrib.sitesis fine and DjangoSEO supports this via theMetadata.Meta.use_sitesattribute. But if the site is initially deployed withMetadata.Meta.use_sites = False, when setting this toTrueof course there's a missing column_site_id.Of course, quickly South comes to my mind, but there's a problem: DjangoSEO is not using migration, and migrations are stored in the app directory, so it would be tinkering with a package inside the site-packages directory.
However I can think on associate the Metadata models with the apps that contains the
seo.pymodule, since the models are being created dynamically, and then the migrations would be inside the VCS tracked app. The developer can change settings, inspect changes with South, generate an apply migrations, all under his app scope.