fix: improve docker deployment stability and ensure prisma migrations run in production
This commit is contained in:
22
Dockerfile
22
Dockerfile
@@ -17,30 +17,36 @@ RUN npm run build
|
||||
FROM node:20-alpine AS runner
|
||||
WORKDIR /app
|
||||
|
||||
# Set production environment
|
||||
ENV NODE_ENV=production
|
||||
ENV PORT=3000
|
||||
ENV DATABASE_URL="file:/app/data/dev.db"
|
||||
|
||||
# Install production dependencies only
|
||||
COPY package*.json ./
|
||||
COPY prisma ./prisma/
|
||||
RUN npm install --omit=dev
|
||||
|
||||
# Copy build artifacts and necessary files
|
||||
COPY --from=builder /app/.next ./.next
|
||||
COPY --from=builder /app/public ./public
|
||||
COPY --from=builder /app/next.config.mjs ./
|
||||
COPY --from=builder /app/next.config.ts ./
|
||||
# Optional: if you have next-pwa and custom worker files
|
||||
# COPY --from=builder /app/public/sw.js ./public/
|
||||
|
||||
# Copy prisma for migrations at runtime
|
||||
COPY --from=builder /app/prisma ./prisma
|
||||
COPY --from=builder /app/node_modules/.prisma ./node_modules/.prisma
|
||||
COPY --from=builder /app/node_modules/@prisma ./node_modules/@prisma
|
||||
|
||||
# Script to run migrations and start the app
|
||||
# Ensure data directory exists
|
||||
RUN mkdir -p /app/data
|
||||
RUN printf "#!/bin/sh\nnpx prisma migrate deploy\nnpm start" > /app/start.sh
|
||||
|
||||
# Script to run migrations and start the app
|
||||
RUN printf "#!/bin/sh\n\
|
||||
set -e\n\
|
||||
echo \"Starting initialization...\"\n\
|
||||
echo \"Database URL: \$DATABASE_URL\"\n\
|
||||
echo \"Running migrations...\"\n\
|
||||
npx prisma migrate deploy\n\
|
||||
echo \"Starting application...\"\n\
|
||||
npm start" > /app/start.sh
|
||||
|
||||
RUN chmod +x /app/start.sh
|
||||
|
||||
EXPOSE 3000
|
||||
|
||||
Reference in New Issue
Block a user