Currently frontend waits for backend to be completely started and then it runs migrate.py. That is on purpose (we do not want multiple migrate.py processes running at once). But we have a migrate.py flag for frontend which, if done properly, could allow them to run simultaneously.
Main thing: do not touch the database at the same time, but the containers could update environments and code (which is in separate containers).
Gain: speed up upgrades between versions (and minimally general startup).
Currently frontend waits for backend to be completely started and then it runs migrate.py. That is on purpose (we do not want multiple migrate.py processes running at once). But we have a migrate.py flag for frontend which, if done properly, could allow them to run simultaneously.
Main thing: do not touch the database at the same time, but the containers could update environments and code (which is in separate containers).
Gain: speed up upgrades between versions (and minimally general startup).