From 33f15f7b5bc1c205f2cc41302644e838a183f1d1 Mon Sep 17 00:00:00 2001 From: parsa aghaei Date: Sat, 15 Aug 2026 18:41:48 +0330 Subject: [PATCH] fix(deploy): seed only on staging, use migrate deploy on production --- scripts/deploy.sh | 17 ++++++++++++++--- 1 file changed, 14 insertions(+), 3 deletions(-) diff --git a/scripts/deploy.sh b/scripts/deploy.sh index 8cde20bd..b6055156 100644 --- a/scripts/deploy.sh +++ b/scripts/deploy.sh @@ -75,8 +75,19 @@ docker compose up -d echo "Waiting for backend to start..." sleep 15 -echo "Running migrations and seeding database..." -docker exec "$CONTAINER_PREFIX" npx prisma db push --accept-data-loss || docker exec "$CONTAINER_PREFIX" npx prisma migrate deploy || true -docker exec "$CONTAINER_PREFIX" npx prisma db seed || true +echo "Running database migrations..." +if [ "$BRANCH" == "develop" ]; then + # Staging: use db push (fast, schema sync) then seed + echo "[STAGING] Running prisma db push..." + docker exec "$CONTAINER_PREFIX" npx prisma db push || true + + echo "[STAGING] Running prisma db seed..." + docker exec "$CONTAINER_PREFIX" npx prisma db seed || true +else + # Production: use migrate deploy only — NEVER seed, NEVER use --accept-data-loss + echo "[PRODUCTION] Running prisma migrate deploy (safe, no data loss)..." + docker exec "$CONTAINER_PREFIX" npx prisma migrate deploy || true + echo "[PRODUCTION] Seeder skipped to protect production data." +fi echo "Deployment for $BRANCH completed successfully!" \ No newline at end of file