[Bookworm] Correct Flask DB migration process
Move the old manage script to _legacy, and add a new _flask version with modern Flask tooling. Decide which one to call via pvc-api-db-migrate using /etc/debian_version call.
This commit is contained in:
@ -11,5 +11,16 @@ if [[ ! -f ${PVC_CONFIG_FILE} ]]; then
|
||||
fi
|
||||
|
||||
pushd /usr/share/pvc
|
||||
./pvcapid-manage.py db upgrade
|
||||
|
||||
case "$( cat /etc/debian_version )" in
|
||||
10.*|11.*)
|
||||
# Debian 10 & 11
|
||||
./pvcapid-manage_legacy.py db upgrade
|
||||
;;
|
||||
*)
|
||||
# Debian 12+
|
||||
flask --app ./pvcapid-manage_flask.py db upgrade
|
||||
;;
|
||||
esac
|
||||
|
||||
popd
|
||||
|
Reference in New Issue
Block a user