From 7e8b5069d48b07848b4d45d096d28d7168822b01 Mon Sep 17 00:00:00 2001 From: ArthurErlich Date: Wed, 2 Sep 2026 21:32:33 +0000 Subject: [PATCH] fix(scripts): update.sh never applied litellm-pgvector's db schema MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit litellm-pgvector's Dockerfile only runs 'prisma generate' (codegen) at build time — nothing ever ran 'prisma db push' against pgvector-db, so the vector_stores/embeddings tables plain didn't exist on a fresh deploy. Every vector store call failed with 'relation "vector_stores" does not exist'. update.sh now runs the push itself after bringing litellm-pgvector up. --- scripts/update.sh | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/scripts/update.sh b/scripts/update.sh index c095d94..274dfe6 100755 --- a/scripts/update.sh +++ b/scripts/update.sh @@ -106,5 +106,15 @@ set -a && . ./.env && set +a echo "==> recreating changed services" docker compose up -d --remove-orphans +# litellm-pgvector's Dockerfile only runs `prisma generate` (codegen) at +# build time — nothing ever applied the schema to pgvector-db itself, so the +# vector_stores/embeddings tables plain didn't exist until this was added +# (see issue #24). --accept-data-loss is the same "no rollback/backup logic, +# git revert is the recovery path" tradeoff as the rest of this script — a +# schema-incompatible change here would need a manual look regardless. +echo "==> syncing litellm-pgvector's database schema" +docker compose up -d --wait pgvector-db litellm-pgvector +docker compose exec -T litellm-pgvector prisma db push --accept-data-loss + echo "==> status" docker compose ps