fix: prisma migrate now runs at container startup + dotenv optional
Deploy to VPS / deploy (push) Has been cancelled

Two related fixes for the deploy pipeline so DB schema changes never
again leave the site half-deployed.

PRISMA CONFIG (prisma.config.ts)
- "import 'dotenv/config'" was hard-required, but dotenv isn't installed
  in the production runtime image (env vars come from docker-compose).
- Wrapped in try/catch so it loads .env locally and silently no-ops in
  the container — `prisma migrate deploy` works in both environments.

DOCKERFILE
- Copies node_modules/prisma + prisma.config.ts to the runner stage so
  the CLI is available at runtime, not just at build.
- New CMD runs `prisma migrate deploy` before booting the server.
  Idempotent — already-applied migrations are skipped. If the DB is
  unreachable, the container exits and docker-compose retries.
- This means: from now on, `git pull && docker compose up -d --build app`
  is the entire deploy. No more "did you remember to run migrations?".

DEFENSIVE TRY/CATCH (applications/[slug]/page.tsx)
- prisma.application.findUnique and prisma.globalNode.findMany now have
  try/catch with logged errors. A transient DB hiccup or missing
  Application slug now degrades gracefully (renders "not found" or empty
  cases wall) instead of triggering a 500 Internal Server Error.

DEPLOY (David, this is the recovery sequence on the VPS)
  cd /opt/flux-srl
  git pull
  docker compose up -d --build app
  # The container will run pending migrations on its own.
  # No need to run `prisma migrate deploy` manually anymore.
This commit is contained in:
2026-05-04 15:04:35 -05:00
parent a199891a3c
commit 01a84edee9
3 changed files with 37 additions and 16 deletions
+9 -2
View File
@@ -54,10 +54,14 @@ COPY --from=builder /app/public ./public
COPY --from=builder --chown=nextjs:nodejs /app/.next/standalone ./ COPY --from=builder --chown=nextjs:nodejs /app/.next/standalone ./
COPY --from=builder --chown=nextjs:nodejs /app/.next/static ./.next/static COPY --from=builder --chown=nextjs:nodejs /app/.next/static ./.next/static
# Copy Prisma schema + generated client (needed for migrations at runtime) # Copy Prisma schema + generated client + CLI binaries (the CLI is needed
# at runtime so the entrypoint can run `prisma migrate deploy` before the
# server boots — avoids the "table does not exist" race after schema changes)
COPY --from=builder /app/prisma ./prisma COPY --from=builder /app/prisma ./prisma
COPY --from=builder /app/prisma.config.ts ./prisma.config.ts
COPY --from=builder /app/node_modules/.prisma ./node_modules/.prisma COPY --from=builder /app/node_modules/.prisma ./node_modules/.prisma
COPY --from=builder /app/node_modules/@prisma ./node_modules/@prisma COPY --from=builder /app/node_modules/@prisma ./node_modules/@prisma
COPY --from=builder /app/node_modules/prisma ./node_modules/prisma
# Copy sharp binary explicitly — Next.js standalone trace usually picks it # Copy sharp binary explicitly — Next.js standalone trace usually picks it
# up, but the @img/sharp-linuxmusl-x64 prebuilt is platform-conditional and # up, but the @img/sharp-linuxmusl-x64 prebuilt is platform-conditional and
@@ -75,4 +79,7 @@ EXPOSE 3000
ENV PORT=3000 ENV PORT=3000
ENV HOSTNAME="0.0.0.0" ENV HOSTNAME="0.0.0.0"
CMD ["node", "server.js"] # Run pending migrations on startup, then boot the Next.js server.
# `migrate deploy` is idempotent — it skips already-applied migrations.
# If the DB is unreachable the container exits and docker-compose retries.
CMD ["sh", "-c", "node ./node_modules/prisma/build/index.js migrate deploy && node server.js"]
+9 -3
View File
@@ -1,7 +1,13 @@
// Local dev loads .env via dotenv. Production (Docker) injects env vars
// directly through docker-compose, so dotenv isn't installed in the runtime
// image — load it conditionally so `prisma migrate deploy` works there too.
try {
// eslint-disable-next-line @typescript-eslint/no-require-imports
require("dotenv/config");
} catch {
// dotenv not installed in this environment — env vars expected from process
}
// This file was generated by Prisma and assumes you have installed the following:
// npm install --save-dev prisma dotenv
import "dotenv/config";
import { defineConfig, env } from "prisma/config"; import { defineConfig, env } from "prisma/config";
export default defineConfig({ export default defineConfig({
+19 -11
View File
@@ -93,9 +93,12 @@ export default async function ApplicationPage({ params }: { params: Promise<{ sl
const { slug, locale } = resolvedParams; const { slug, locale } = resolvedParams;
// 1. Buscamos la Teoría General de la Aplicación // 1. Buscamos la Teoría General de la Aplicación
const rawData = await prisma.application.findUnique({ let rawData: any = null;
where: { slug } try {
}); rawData = await prisma.application.findUnique({ where: { slug } });
} catch (error) {
console.error(`[applications/${slug}] DB error fetching application:`, error);
}
if (!rawData) { if (!rawData) {
return ( return (
@@ -110,14 +113,19 @@ export default async function ApplicationPage({ params }: { params: Promise<{ sl
const data = getLocalizedData(rawData, locale); const data = getLocalizedData(rawData, locale);
// 2. Buscamos el "Muro de Soluciones" (Casos Reales específicos de esta app) // 2. Buscamos el "Muro de Soluciones" (Casos Reales específicos de esta app)
const rawRealCases = await prisma.globalNode.findMany({ let rawRealCases: any[] = [];
where: { try {
application: slug, rawRealCases = await prisma.globalNode.findMany({
isActive: true, where: {
projectOverview: { not: null } application: slug,
}, isActive: true,
orderBy: { createdAt: 'desc' } projectOverview: { not: null },
}); },
orderBy: { createdAt: "desc" },
});
} catch (error) {
console.error(`[applications/${slug}] DB error fetching cases:`, error);
}
// 🔥 TRADUCIMOS TODOS LOS CASOS DE ESTUDIO DEL MURO // 🔥 TRADUCIMOS TODOS LOS CASOS DE ESTUDIO DEL MURO
const realCases = rawRealCases.map((node: any) => getLocalizedData(node, locale)); const realCases = rawRealCases.map((node: any) => getLocalizedData(node, locale));