Dockerfile.controller

# Controller image — Next.js standalone build.
FROM node:22-alpine AS build
WORKDIR /app
COPY package.json package-lock.json* ./
COPY packages/shared/package.json packages/shared/
COPY packages/controller/package.json packages/controller/
COPY packages/agent/package.json packages/agent/
RUN npm install --ignore-scripts
COPY packages/shared packages/shared
COPY packages/controller packages/controller
# A dummy URL lets `prisma generate` load prisma.config.ts at build time.
# No DB connection happens during generate/build; the real URL is set at runtime.
ENV DATABASE_URL="postgresql://build:build@localhost:5432/build"
RUN npm run build --workspace @cbm/shared \
  && npm run build --workspace @cbm/controller

FROM node:22-alpine AS runtime
WORKDIR /app
ENV NODE_ENV=production
ENV PORT=3000
# pg_dump/pg_restore for the controller's metadata self-backup + recovery-file
# import (disaster recovery). Match the compose Postgres major (17).
RUN apk add --no-cache postgresql17-client
# Standalone server bundle (includes traced node_modules).
COPY --from=build /app/packages/controller/.next/standalone ./
COPY --from=build /app/packages/controller/.next/static ./packages/controller/.next/static
# Prisma assets + full node_modules so `prisma migrate deploy` works at startup.
COPY --from=build /app/packages/controller/prisma ./packages/controller/prisma
COPY --from=build /app/packages/controller/prisma.config.ts ./packages/controller/prisma.config.ts
COPY --from=build /app/node_modules ./node_modules
EXPOSE 3000
# Pad any legacy migration names (one-time, idempotent), apply migrations, then
# start the standalone server.
CMD ["sh", "-c", "cd /app/packages/controller && (npx prisma db execute --file ./prisma/pad-migrations.sql || echo 'pad skipped') && (npx prisma migrate deploy || echo 'migrate skipped') && cd /app && node packages/controller/server.js"]