I'm aware of this option, but it is a dictionary with application name
as a key, right ? How can I tell Django to look for /cartridge.shop/
migrations both at original path and my extension package ?
In this case the application name is just /shop/. After setting up
MIGRATION_MODULES, your first run of `makemigrations` will squash the
existing migrations into one file and your extension package will be the
only place django looks for /shop/ migrations from now on. This means
you'll need to ship any future migrations in cartridge yourself.
I'm not sure what you're thinking on this, but I would document how to
make the necessary changes to EXTRA_MODEL_FIELDS and MIGRATION_MODULES
as part of the installation process rather than modifying them in your app.
--
You received this message because you are subscribed to the Google Groups "Mezzanine
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
