next.js
d7732c57 - [feat] Added Docker examples for standalone output and export output following best practices (#87069)

Commit
68 days ago
[feat] Added Docker examples for standalone output and export output following best practices (#87069) ## What? Modernizes the existing `with-docker` example and adds a new `with-docker-export-output` example demonstrating different Next.js deployment strategies with Docker best practices: 1. **`with-docker` (updated)** - Modernized to use App Router, TypeScript, Tailwind CSS v4, and comprehensive Docker best practices. Now includes both Node.js and Bun Dockerfile options, Docker Compose with profiles, BuildKit cache mounts, and extensive documentation. 2. **`with-docker-export-output` (new)** - Demonstrates Next.js static export mode deployment with Docker, offering two serving options: **Nginx** (production-grade) and **serve** package (Node.js-based, simpler setup). Includes optimized Nginx configuration, BuildKit cache mounts, and comprehensive documentation. Both examples include detailed documentation explaining Docker best practices, implementation decisions, and deployment guidance. ## Why? The existing `with-docker` example was using the Pages Router and lacked: - Modern Next.js patterns (App Router, TypeScript) - Detailed documentation explaining Docker best practices and implementation decisions - BuildKit cache mounts for optimized build performance - Bun runtime support as an alternative to Node.js - Docker Compose configurations for easier local development - Clear documentation about Node.js image variant choices (slim vs Alpine) - Examples demonstrating static export mode These updates serve as comprehensive references for developers who want to understand: - How to Dockerize Next.js applications for different deployment scenarios - Why certain choices are made and how to optimize Docker setups for production - When to use standalone mode vs static export mode - How to choose between Node.js and Bun runtimes - How to choose between different web servers (Nginx vs serve) for static sites ## How? ### `with-docker` example (updated) - **Migrated to App Router** with TypeScript and Tailwind CSS v4 - **Multi-stage Dockerfile** with three stages: dependencies installation, build, and runtime - **Bun support** via `Dockerfile.bun` with optimized configuration - **BuildKit cache mounts** for package manager stores (`npm`, `yarn`, `pnpm`, `bun`) and Next.js build cache - **Security best practices** with non-root user execution (built-in `node` and `bun` users) - **Docker Compose configuration** with profiles for Node.js (default) and Bun - **Comprehensive `.dockerignore`** to minimize build context size - **Detailed README** explaining standalone mode benefits, Node.js image choices, and deployment guidance - **Deleted** `with-docker-standalone-output` (merged into this example) ### `with-docker-export-output` example (new) - **Two Dockerfile options:** - `Dockerfile` - Nginx-based serving with `nginxinc/nginx-unprivileged` for security - `Dockerfile.serve` - Node.js serve package-based serving for simpler deployments - **Multi-stage builds** for both options with separate dependency, build, and runtime stages - **BuildKit cache mounts** for package manager stores and Next.js build cache - **Production Nginx configuration** (`nginx.conf`) with gzip compression, caching headers, and security best practices - **Docker Compose configuration** supporting both serving options via profiles - **Comprehensive README** explaining static export mode, trade-offs between Nginx and serve ### Docker best practices implemented (both examples) | Practice | Description | |----------|-------------| | Multi-stage builds | Optimal image size reduction | | Layer caching | Package files copied first | | Minimal build context | Comprehensive `.dockerignore` files | | BuildKit cache mounts | Faster subsequent builds | | Security hardening | Non-root user execution | | Corepack | yarn/pnpm version management | | Package manager auto-detection | npm, yarn, pnpm support | | Node.js 24.13.0-slim | Clear upgrade guidance | ## Breaking Changes > **Warning** > - `with-docker` now uses App Router instead of Pages Router > - `with-docker-standalone-output` has been removed (merged into `with-docker`) --- **Note:** After this PR is approved and merged, I plan to open a follow-up PR to update the Next.js documentation with proper links to these Docker examples. --------- Co-authored-by: Wyatt Johnson <accounts+github@wyattjoh.ca> Co-authored-by: Joseph <joseph.chamochumbi@vercel.com> Co-authored-by: kristiyan.velkov <kristiyan.velkov@ffw.com>
Parents
Loading