Fix Dockerfile for NextAuth + Prisma deployment

Add Prisma support to Docker build:
- Run 'prisma generate' during Docker build
- Copy Prisma client and schema to production image
- Remove 'prisma db push' from build script (runs at startup)
- Enable Next.js standalone output mode
- Add db-setup.sh script for runtime migrations

This fixes the deployment failure where Prisma wasn't available.

Co-authored-by: Cursor <cursoragent@cursor.com>

Dockerfile

@@ -25,7 +25,10 @@ COPY . .
 ENV NEXT_TELEMETRY_DISABLED=1
 ENV NODE_ENV=production
 
-# Build the application
+# Generate Prisma Client (needs schema but not DATABASE_URL yet)
+RUN npx prisma generate
+
+# Build the application (DATABASE_URL will be available via Coolify env vars)
 RUN npm run build
 
 # Production image, copy all the files and run next
@@ -43,6 +46,11 @@ COPY --from=builder /app/public ./public
 COPY --from=builder --chown=nextjs:nodejs /app/.next/standalone ./
 COPY --from=builder --chown=nextjs:nodejs /app/.next/static ./.next/static
 
+# Copy Prisma files for runtime
+COPY --from=builder /app/node_modules/.prisma ./node_modules/.prisma
+COPY --from=builder /app/node_modules/@prisma ./node_modules/@prisma
+COPY --from=builder /app/prisma ./prisma
+
 USER nextjs
 
 EXPOSE 3000

package.json

@@ -4,7 +4,7 @@
   "private": true,
   "scripts": {
     "dev": "next dev",
-    "build": "prisma generate && prisma db push --accept-data-loss && next build",
+    "build": "next build",
     "start": "next start",
     "lint": "eslint",
     "postinstall": "prisma generate",

scripts/db-setup.sh

@@ -0,0 +1,7 @@
+#!/bin/sh
+# Run database migrations at container startup
+# This ensures DATABASE_URL is available from Coolify env vars
+
+echo "Running Prisma DB setup..."
+npx prisma db push --accept-data-loss --skip-generate
+echo "Database setup complete!"