fix: use prisma db push in entrypoint instead of migrate deploy
Some checks failed
Deploy to Production / Build and Deploy (push) Has been cancelled
Some checks failed
Deploy to Production / Build and Deploy (push) Has been cancelled
The app uses db push (no migration files), so migrate deploy was a no-op. Also removes the redundant migration step from deploy.yaml since the entrypoint now handles schema sync on every container start. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
@@ -1,8 +1,8 @@
|
||||
#!/bin/sh
|
||||
set -e
|
||||
|
||||
echo "Running Prisma migrations..."
|
||||
node ./node_modules/prisma/build/index.js migrate deploy
|
||||
echo "Syncing database schema..."
|
||||
node ./node_modules/prisma/build/index.js db push --skip-generate
|
||||
|
||||
echo "Starting server..."
|
||||
exec node server.js
|
||||
|
||||
Reference in New Issue
Block a user