Dockerfile

Rama main · réplica de lectura del repositorio original.

FROM node:20-alpine AS base

FROM base AS deps
WORKDIR /app
COPY package.json package-lock.json ./
RUN npm ci

FROM base AS builder
WORKDIR /app
COPY --from=deps /app/node_modules ./node_modules
COPY . .
# Prisma generate needs a syntactically valid DATABASE_URL but never connects.
# Inline it so it does not persist as an image layer.
RUN DATABASE_URL="postgresql://build:build@localhost/build" npx prisma generate
# The build needs no network: fonts are self-hosted (app/fonts.ts). Without a
# network a dependency that starts downloading at build time fails here.
RUN --network=none npm run build
# The worker process (docker-compose.yml "worker" service) as one file. The
# runner stage has no TypeScript runtime and the standalone output only holds
# what server.js needs; Prisma stays external and resolves from its node_modules.
RUN --network=none node scripts/build-worker.mjs /app/worker.cjs
# Stage the Prisma CLI with its FULL runtime dependency closure for the
# runner. Computed from the installed tree, not hand-listed: a partial copy
# shipped an image that crashed at start with MODULE_NOT_FOUND (issue #27).
RUN node scripts/stage-prisma-cli.mjs /app/prisma-cli

FROM base AS runner
WORKDIR /app
ENV NODE_ENV=production
RUN addgroup --system --gid 1001 nodejs
RUN adduser --system --uid 1001 nextjs
COPY --from=builder /app/public ./public
COPY --from=builder /app/.next/standalone ./
COPY --from=builder /app/.next/static ./.next/static
COPY --from=builder /app/prisma ./prisma
COPY --from=builder /app/node_modules/.prisma ./node_modules/.prisma
COPY --from=builder /app/worker.cjs ./worker.cjs
# Prisma CLI + full runtime dependency closure, staged by
# scripts/stage-prisma-cli.mjs in the builder (see issue #27: hand-copied
# subsets missed transitive deps and the container crash-looped at start).
# Still no npm invocation in this stage — a second npm install under QEMU
# arm64 emulation intermittently crashes with SIGILL (see PR #23).
COPY --from=builder /app/prisma-cli ./node_modules
USER nextjs
EXPOSE 3000
ENV PORT=3000
ENV HOSTNAME=0.0.0.0
# Invoke the CLI's real entry point, not node_modules/.bin/prisma: COPY
# flattens that symlink into a file, and the CLI then resolves its WASM
# relative to the wrong directory (fault 3 of issue #27).
# The web app (migrations first). The worker service starts the same image
# with `node worker.cjs` instead.
CMD ["sh", "-c", "node node_modules/prisma/build/index.js migrate deploy && node server.js"]