Hey, I have two issues I'm looking at solving at work, and I'm looking for a couple suggestions as to how other people have solved this. The two things are:
* scale out their django installation to allow for smaller releases (I'm thinking microservices, but it could also be internal django apps or who knows what else) * minimizing the impact of migrations during releases (aka we want to be able to release in the middle of the afternoon Currently we put up a maintenance page whenever we are doing database operations (aka migrations). This seems like a recommended best practice. One way I was thinking about addressing this issue was to break all of our models out into a separate repo. That way we'd only need to deploy migrations when the models themselves have deployed. For code that needs the models, we could pip install the repo as an app and away we go. Likewise it seems like I could break up different parts of our app via a similar strategy. Does this seem viable? How have other people solved this kind of problem? Thanks, -Ben -- 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/e5fd0359-9e8b-4cce-b3e1-4880951a2a8e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
