From 52861e29a9fecd0b94bcf269b12a877eee5eb1c7 Mon Sep 17 00:00:00 2001
From: Lucas Santana <lucas.diassantana@gmail.com>
Date: Sat, 14 Mar 2026 14:51:30 -0300
Subject: [PATCH] fix(deploy): pin prisma config for webhook migrations

---
 CHANGELOG.md      | 6 ++++++
 README.md         | 3 +++
 scripts/deploy.sh | 6 ++++--
 3 files changed, 13 insertions(+), 2 deletions(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 6f779836f..8978a628e 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -7,6 +7,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+### Fixed
+
+- Pinned webhook-driven `prisma migrate deploy` and `prisma migrate status`
+  calls to `prisma/prisma.config.ts` so homelab deploys keep `DATABASE_URL`
+  resolution when run from the webhook container.
+
 ## [2.6.15] - 2026-03-14
 
 ### Added
diff --git a/README.md b/README.md
index da8b3e544..897556d1b 100644
--- a/README.md
+++ b/README.md
@@ -371,6 +371,9 @@ contract success, instead of failing the rollout as a false negative.
 Deploy webhook rollout now starts `postgres`/`redis`, runs
 `prisma migrate deploy`, and executes a `guild_role_grants` relation preflight
 before service rollout to fail fast on schema drift.
+When those Prisma migration commands run from the webhook container, they must
+pin `prisma/prisma.config.ts` (and `prisma/schema.prisma`) explicitly so the
+deploy path keeps `DATABASE_URL` resolution deterministic.
 CLOUDFLARED tunnel restarts now mount config from `CLOUDFLARED_CONFIG_DIR`
 instead of shell `$HOME`; use a canonical host path like
 `/home/luk-server/.cloudflared` to avoid deploy-context mount drift.
diff --git a/scripts/deploy.sh b/scripts/deploy.sh
index 5074bf537..7e56c23a9 100755
--- a/scripts/deploy.sh
+++ b/scripts/deploy.sh
@@ -286,14 +286,16 @@ log "Starting database services..."
 docker_compose up -d postgres redis
 
 log "Running database migrations..."
-if ! docker_compose run --rm --no-deps backend sh -lc "npx prisma migrate deploy"; then
+if ! docker_compose run --rm --no-deps backend \
+    sh -lc "npx prisma migrate deploy --config prisma/prisma.config.ts --schema prisma/schema.prisma"; then
     log "ERROR: prisma migrate deploy failed (migration execution error)"
     notify 16711680 "Deploy Failed" "Database migration failed"
     exit 1
 fi
 
 log "Checking migration status..."
-if ! docker_compose run --rm --no-deps backend sh -lc "npx prisma migrate status"; then
+if ! docker_compose run --rm --no-deps backend \
+    sh -lc "npx prisma migrate status --config prisma/prisma.config.ts --schema prisma/schema.prisma"; then
     log "ERROR: prisma migrate status failed (migration drift/history mismatch)"
     notify 16711680 "Deploy Failed" "Database migration status guard failed"
     exit 1