-
|
Hi, Question: The docker-compose.yml files in the repos use Thanks for any response. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
hey, I tested the DB/migration path on a fresh 18 DB and it works. The repo still pins The catch is existing data. Do not reuse the same |
Beta Was this translation helpful? Give feedback.
hey, I tested the DB/migration path on a fresh 18 DB and it works.
The repo still pins
postgres:15-alpinein compose/prod/k8s/CI, but the backend is just SQLAlchemy + asyncpg throughDATABASE_URL. I ran the Alembic migrations against a freshpostgres:18-alpineDB andupgrade headcompleted cleanly. Running it a second time was a no-op at the same head.The catch is existing data. Do not reuse the same
postgres_datavolume from 15 after changing the tag. I tested that too and 18 refused the 15-initialized data dir. So for a new private install, 18 looks fine to try. For an existing install, do dump/restore orpg_upgrade, not just an image-tag swap.