# ─── Stage 1: Build ──────────────────────────────────────────────────────────
FROM node:20-slim AS builder

WORKDIR /app

RUN apt-get update -qq && apt-get install -y -qq openssl python3 && rm -rf /var/lib/apt/lists/*

COPY package.json package-lock.json ./
COPY backend/package.json ./backend/
COPY frontend/package.json ./frontend/
COPY backend/prisma ./backend/prisma

RUN npm ci

COPY backend/src ./backend/src
COPY backend/tsconfig*.json ./backend/

RUN cd backend && npx prisma generate && npx tsc -p tsconfig.build.json

# ─── Stage 2: Runtime ────────────────────────────────────────────────────────
FROM node:20-slim AS runtime

WORKDIR /app

RUN apt-get update -qq && apt-get install -y -qq openssl && rm -rf /var/lib/apt/lists/*

COPY package.json package-lock.json ./
COPY backend/package.json ./backend/
COPY frontend/package.json ./frontend/
COPY backend/prisma ./backend/prisma

# Reuse the builder's node_modules: it already contains bcrypt's compiled
# native addon (built WITH install scripts) and the generated Prisma client.
# A fresh `npm ci --ignore-scripts` here omits bcrypt's *.node binary, so the
# app crash-loops at runtime ("Cannot find module .../bcrypt_lib.node") — both
# the seed and NestJS auth require bcrypt. builder and runtime share the same
# node:20-slim base, so the native binaries are ABI/platform-compatible.
COPY --from=builder /app/node_modules ./node_modules

COPY --from=builder /app/backend/dist ./backend/dist
COPY backend/entrypoint.sh /entrypoint.sh
RUN chmod +x /entrypoint.sh

WORKDIR /app/backend

EXPOSE 3001

ENV PORT=3001
ENV NODE_ENV=production

ENTRYPOINT ["/entrypoint.sh"]