root/sase.tr
1
0
Fork 0
Code Issues 5 Pull Requests 3 Actions 1 Packages Projects Releases Wiki Activity

fix(deploy): remove pnpm db:push from automated deploy

Browse Source 
The interactive Drizzle prompt on destructive schema changes
(column/index drops with row-level data warnings) cannot be
answered over a non-interactive SSH session, causing the deploy
to hang. Schema migrations now run manually so they get the
review they need.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Sase Dev
2026-05-10 08:23:44 +00:00
parent e2de198a07
commit 73a55c68ad
1 changed files with 7 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
scripts/deploy.sh
View File

@@ -47,11 +47,13 @@ log "Pre-rendering public pages..."
pnpm prerender || log "WARNING: Pre-render failed (non-fatal, continuing deploy)"
cd "$DEPLOY_DIR"
# ── Step 4: Database migrations (safe push) ──
log "Running database migrations (drizzle-kit push)..."
cd apps/api
pnpm db:push || error_exit "Database migration failed"
cd "$DEPLOY_DIR"
# ── Step 4: Database migrations (manual) ──
# Schema migrations are NOT run automatically.
# `pnpm db:push` is interactive and may prompt for destructive changes
# (column drops, etc.) which cannot be answered over a non-interactive
# SSH session. Run schema changes manually from apps/api:
# pnpm db:push # interactive, dev/staging
# pnpm db:generate # produce a versioned migration (recommended for prod)
# ── Step 5: Zero-downtime PM2 reload ──
log "Reloading PM2 processes (zero-downtime)..."