My thought process for separating the models into a separate repo is
something like this:
I am predominately putting up our (heroku) maintenace page when migrations
are run
If the models are in separte repo, I only need to run migrations when that
repo is deployed. If migrations are not deploy
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 ap
2 matches
Mail list logo
