You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been using the Mozilla fork since 2019. They added /app/manage.py db upgrade to the server/worker/scheduler entrypoint. When I tried the same thing on 24.06.0-dev, the database was successfully upgraded but then the server container exited with code 0
From the documentation and this discussion #6567, looks like the protocol at the moment is executing ./bin/docker-entrypoint manage db upgrade manually on the server. Am I correct?
Since I'm using k8s and k9scli, I just shell into a running container and execute ./bin/docker-entrypoint manage db upgrade, which is not a big deal. But I am looking forward to an automated db migration mechanism.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I've been using the Mozilla fork since 2019. They added
/app/manage.py db upgrade
to the server/worker/scheduler entrypoint. When I tried the same thing on24.06.0-dev
, the database was successfully upgradedbut then the server container exited with code 0From the documentation and this discussion #6567, looks like the protocol at the moment is executing
./bin/docker-entrypoint manage db upgrade
manually on the server. Am I correct?Since I'm using k8s and k9scli, I just shell into a running container and execute
./bin/docker-entrypoint manage db upgrade
, which is not a big deal. But I am looking forward to an automated db migration mechanism.Beta Was this translation helpful? Give feedback.
All reactions