tyler
bb6dbe37a4
Ports the deploy pipeline from the Gitea main fork (commit 7ddb06d's deploy toolkit) into the Auth.js v5 / NextAuth tree: - .gitea/workflows/deploy.yml: inline deploy that brings up the Docker stack, applies migrations, builds Next.js, and runs the app under PM2. Swapped Better Auth env vars (BETTER_AUTH_SECRET/URL, NEXT_PUBLIC_BETTER_AUTH_URL) for Auth.js v5 names (AUTH_SECRET/URL, NEXT_PUBLIC_AUTH_URL). Dropped NEXT_PUBLIC_SUPABASE_URL/ANON_KEY (Supabase removal in progress). Added GOOGLE_CLIENT_ID/SECRET + ALLOW_DEV_LOGIN for the Auth.js Google provider and dev credentials path. Switched runs-on from 'ubuntu-latest' to the self-hosted runner labels matching build.yml. - deploy/: idempotent deploy toolkit (deploy.sh, docker-compose.yml, Dockerfile.nextjs, nginx.conf.template, .env.production.example, healthcheck.sh, Makefile, deploy/.gitignore). No auth/Supabase dependencies — pure infra. - deploy/.env.production.example: renamed NEXTAUTH_SECRET/NEXTAUTH_URL (v4) to AUTH_SECRET/AUTH_URL (v5) and added the v5-specific vars (NEXT_PUBLIC_AUTH_URL, GOOGLE_*, ALLOW_DEV_LOGIN). Build pipeline is now end-to-end: build.yml → typecheck + lint + build (uses [self-hosted, linux, ubuntu-latest]) deploy.yml → start docker stack + migrations + build + PM2 restart Storage / admin code ports (MinIO via @/lib/storage, Supabase removal, admin-permissions rewrite) are tracked separately — they require porting the storage and admin code first; the deploy pipeline itself is ready to run against the Auth.js world.
58 lines
2.2 KiB
Docker
58 lines
2.2 KiB
Docker
# =============================================================================
|
|
# Dockerfile.nextjs — multi-stage build for the Next.js frontend
|
|
# =============================================================================
|
|
# Used by docker-compose.yml's `nextjs` service.
|
|
#
|
|
# Why this looks the way it does:
|
|
# - `NEXT_PUBLIC_API_URL` must be present at BUILD time (Next.js inlines
|
|
# it into the client JS). We pass it through as an ARGs so the build
|
|
# context is reproducible (`docker build --build-arg` or via deploy.sh's
|
|
# `docker compose --env-file` flow).
|
|
# - We copy the host's pre-built `.next/` (produced by `npm run build` in
|
|
# deploy.sh) rather than running `next build` inside the image. This
|
|
# keeps the image lean and avoids double-building.
|
|
# =============================================================================
|
|
|
|
# ---- builder: produce node_modules with dev deps for the build step --------
|
|
FROM node:20-alpine AS deps
|
|
WORKDIR /app
|
|
COPY package.json package-lock.json* ./
|
|
RUN if [ -f package-lock.json ]; then npm ci; else npm install; fi
|
|
|
|
# ---- builder: produce the standalone .next/ output ------------------------
|
|
FROM node:20-alpine AS builder
|
|
WORKDIR /app
|
|
COPY --from=deps /app/node_modules ./node_modules
|
|
COPY . .
|
|
|
|
# These ARGs are wired through docker-compose's `args:` block (or the CLI).
|
|
# deploy.sh exports them in the build environment.
|
|
ARG NEXT_PUBLIC_API_URL
|
|
ENV NEXT_PUBLIC_API_URL=${NEXT_PUBLIC_API_URL}
|
|
ARG NEXTJS_HOST_PORT
|
|
ENV NEXTJS_HOST_PORT=${NEXTJS_HOST_PORT}
|
|
|
|
RUN npm run build
|
|
|
|
# ---- runner: minimal image, standalone server -----------------------------
|
|
FROM node:20-alpine AS runner
|
|
WORKDIR /app
|
|
ENV NODE_ENV=production
|
|
ENV PORT=3000
|
|
|
|
# Run as non-root.
|
|
RUN addgroup --system --gid 1001 nodejs \
|
|
&& adduser --system --uid 1001 nextjs
|
|
|
|
# Copy only what the standalone server needs.
|
|
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/public ./public
|
|
|
|
USER nextjs
|
|
EXPOSE 3000
|
|
|
|
# Adjust this CMD to match the actual server file your build emits.
|
|
# For `output: "standalone"` in next.config.js the file is server.js.
|
|
CMD ["node", "server.js"]
|