Hi! I have a problem with migrations workflow for which I couldn't find an answer anywhere else.
Suppose, that I have an application MYAPP, that uses some third-party apps. These third-party apps require running `makemigrations` command after adding them to INSTALLED_APPS, because their migrations depend on settings and therefore can't be distributed right away. I.e. take `django-modeltranslation` whose migrations depends on `LANGUAGES` setting or `django-money` whose migrations depends on `CURRENCIES` setting. If I was the only user of MYAPP, I would just generate these migrations depending on my settings and that would be it. What's important that these migrations belong to application MYAPP, not to third-party apps. But, I also want to distribute my application MYAPP to other users. I don't know what they settings will look like, so they'll also need to generate their own migrations. Now, I release new version of MYAPP. This version may contain some MYAPP models related migrations. How should the other users proceed to upgrade MYAPP to new version and still retain their settings-dependent migrations? Is there any straightforward elegant solution? Or at least some nasty/ugly agreed upon "standard" solution? I can't believe that I'm the only one who has this problem. Regards, JM -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/9666391b-093d-2ae9-2cae-3a3b58db87e7%40nic.cz. For more options, visit https://groups.google.com/d/optout.
