Skip to main content
nextjs-deployment Provides comprehensive patterns for deploying Next.js applications to production. Use when configuring Docker containers, setting up GitHub Actions CI/CD pipelines, managing environment variables, implementing preview deployments, or setting up monitoring and logging for Next.js applications. Covers standalone output, multi-stage Docker builds, health checks, OpenTelemetry instrumentation, and production best practices.
Aller à l'installation Skills Marketplace Découvrez et explorez les compétences IA créées par la communauté.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Afficher les détails du prompt Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
npx skills add https://github.com/giuseppe-trisciuoglio/developer-kit --skill nextjs-deploymentLa commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.
Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.
Télécharger Zip Téléchargement... Plus depuis ce dépôt Posts review findings from a JSON file as inline comments on a GitHub Pull Request, attaching each comment to its file and line. Use when you have a list/JSON of review findings (each with a file path, line number, and a message such as summary/failure_scenario) and want them published on a PR as inline review comments. Triggers include "post these review comments on the PR", "associate comments to files in the PR", "publish review findings to PR
typescript-security-review Provides security review capability for TypeScript/Node.js applications, validates code against XSS, injection, CSRF, JWT/OAuth2 flaws, dependency CVEs, and secrets exposure. Use when performing security audits, before deployment, reviewing authentication/authorization implementations, or ensuring OWASP compliance for Express, NestJS, and Next.js. Triggers on "security review", "check for security issues", "TypeScript security audit".
Initialize Spec-Driven Development context — detects tech stack, conventions, architecture patterns, and bootstraps persistence backends. Triggers on 'sdd-init', 'init sdd', 'setup sdd', 'initialize sdd', 'setup project', 'initialize project context'. Creates/updates docs/specs/architecture.md & ontology.md (Constitution), and populates knowledge-graph.json.
Explorateur de fichiers
5 fichiers Métiers associés SOC
Basé sur la classification professionnelle SOC
name nextjs-deployment description Provides comprehensive patterns for deploying Next.js applications to production. Use when configuring Docker containers, setting up GitHub Actions CI/CD pipelines, managing environment variables, implementing preview deployments, or setting up monitoring and logging for Next.js applications. Covers standalone output, multi-stage Docker builds, health checks, OpenTelemetry instrumentation, and production best practices. allowed-tools Read, Write, Edit, Bash
Next.js Deployment
Deploy Next.js applications to production with Docker, CI/CD pipelines, and comprehensive monitoring.
Overview
This skill provides patterns and code examples for deploying Next.js applications to production environments. It covers containerization with Docker, CI/CD automation with GitHub Actions, environment configuration, health checks, and production monitoring. Use standalone output mode for container deployments, multi-stage Docker builds for optimized images, and OpenTelemetry for observability.
When to Use
Activate when user requests involve:
"Deploy Next.js", "Dockerize Next.js", "containerize"
"GitHub Actions", "CI/CD pipeline", "automated deployment"
"Environment variables", "runtime config", "NEXT_PUBLIC"
"Preview deployment", "staging environment"
"Monitoring", "OpenTelemetry", "tracing", "logging"
"Health checks", "readiness", "liveness"
"Production build", "standalone output"
"Server Actions encryption key", "NEXT_SERVER_ACTIONS_ENCRYPTION_KEY"
Quick Reference
Output Modes
standaloneDocker/container deployment output: 'standalone'exportStatic site (no server) output: 'export'(default) Node.js server deployment next start
Environment Variable Types Prefix Availability Use Case NEXT_PUBLIC_Build-time + Browser Public API keys, feature flags (no prefix) Server-only Database URLs, secrets Runtime Server-only Different values per environment
Key Files File Purpose DockerfileMulti-stage container build .github/workflows/deploy.ymlCI/CD pipeline next.config.tsBuild configuration instrumentation.tsOpenTelemetry setup src/app/api/health/route.tsHealth check endpoint
Instructions
1. Configure Standalone Output
import type { NextConfig } from 'next'
const nextConfig : NextConfig = {
output : 'standalone' ,
poweredByHeader : false ,
generateBuildId : async () => process.env .GIT_HASH || 'build' ,
}
export default nextConfig
2. Create Dockerfile # syntax=docker/dockerfile:1
FROM node:20-alpine AS base
FROM base AS deps
RUN apk add --no-cache libc6-compat
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 . .
ENV NEXT_TELEMETRY_DISABLED=1 NODE_ENV=production
ARG GIT_HASH NEXT_SERVER_ACTIONS_ENCRYPTION_KEY
ENV GIT_HASH=${GIT_HASH} NEXT_SERVER_ACTIONS_ENCRYPTION_KEY=${NEXT_SERVER_ACTIONS_ENCRYPTION_KEY}
RUN npm run build
FROM base AS runner
WORKDIR /app
ENV NODE_ENV=production NEXT_TELEMETRY_DISABLED=1 PORT=3000 HOSTNAME="0.0.0.0"
RUN addgroup --system --gid 1001 nodejs && adduser --system --uid 1001 nextjs
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
HEALTHCHECK --interval=30s --timeout=5s --start-period=5s --retries=3 \
CMD node -e "require('http').get('http://localhost:3000/api/health', (r) => r.statusCode === 200 ? process.exit(0) : process.exit(1))"
CMD ["node", "server.js"]
3. Set Up GitHub Actions
name: Build and Deploy
on:
push:
branches: [main , develop ]
env:
REGISTRY: ghcr.io
IMAGE_NAME: ${{ github.repository }}
jobs:
build:
runs-on: ubuntu-latest
permissions:
contents: read
packages: write
steps:
- uses: actions/checkout@v4
- uses: docker/setup-buildx-action@v3
- uses: docker/login-action@v3
with:
registry: ${{ env.REGISTRY }}
username: ${{ github.actor }}
password: ${{ secrets.GITHUB_TOKEN }}
- id: meta
uses: docker/metadata-action@v5
with:
images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
- id: generate-key
run: echo "key=$(openssl rand -base64 32)" >> $GITHUB_OUTPUT
- uses: docker/build-push-action@v5
with:
context: .
push: true
tags: ${{ steps.meta.outputs.tags }}
cache-from: type=gha
cache-to: type=gha,mode=max
build-args: |
GIT_HASH=${{ github.sha }}
NEXT_SERVER_ACTIONS_ENCRYPTION_KEY=${{ steps.generate-key.outputs.key }}
4. Configure Environment Variables
export function getEnv (return {
databaseUrl : process.env .DATABASE_URL !,
apiKey : process.env .API_KEY !,
publicApiUrl : process.env .NEXT_PUBLIC_API_URL !,
}
}
export function validateEnv (const required = ['DATABASE_URL' , 'API_KEY' , 'NEXT_PUBLIC_API_URL' ]
const missing = required.filter ((key ) => !process.env [key])
if (missing.length > 0 ) {
throw new Error (`Missing required environment variables: ${missing.join(', ' )} ` )
}
}
5. Implement Health Checks
import { NextResponse } from 'next/server'
export const dynamic = 'force-dynamic'
export async function GET (const checks = {
status : 'healthy' ,
timestamp : new Date ().toISOString (),
version : process.env .npm_package_version || 'unknown' ,
uptime : process.uptime (),
}
return NextResponse .json (checks)
}
6. Set Up Monitoring
import { registerOTel } from '@vercel/otel'
export function register (registerOTel ({
serviceName : process.env .OTEL_SERVICE_NAME || 'next-app' ,
})
}
7. Handle Server Actions Encryption CRITICAL : Generate and set consistent encryption key for multi-server deployments:
Without this key, Server Actions fail with "Failed to find Server Action" errors in multi-server deployments.
Best Practices
Docker : Use multi-stage builds, enable standalone output, set non-root user, include health checksSecurity : Never commit .env.local, use NEXT_PUBLIC_ only for public values, set NEXT_SERVER_ACTIONS_ENCRYPTION_KEYPerformance : Use output: 'standalone', enable CDN for static assets, use next/imageEnvironment : Use same Docker image across environments, inject runtime config via env vars
Examples
const nextConfig = {
output : 'standalone' ,
poweredByHeader : false ,
compress : true ,
generateBuildId : async () => process.env .GIT_HASH || 'build' ,
}
export default nextConfig
version: '3.8'
services:
app:
build: .
ports:
- "3000:3000"
environment:
- DATABASE_URL=postgresql://db:5432/myapp
- NEXT_PUBLIC_API_URL=http://localhost:3000/api
Constraints and Warnings
Constraints
Standalone output requires Node.js 18+
Server Actions encryption key must be consistent across all instances
Runtime environment variables only work with output: 'standalone'
OpenTelemetry requires instrumentation.ts at project root
Warnings
Never use NEXT_PUBLIC_ prefix for sensitive valuesAlways set NEXT_SERVER_ACTIONS_ENCRYPTION_KEY for multi-server deployments
Without health checks, orchestrators may send traffic to unhealthy instances
Runtime env vars don't work with static export (output: 'export')
References
references/docker-patterns.md references/github-actions.md references/monitoring.md references/deployment-platforms.md 