Building Next.js with the right public environment values Next.js public environment values can be embedded into browser JavaScript during the build. Changing only a running server variable may leave visitors…

Choosing a static export or a Next.js server deployment Next.js can produce a static website or run as an application server. Choose the deployment mode from the features your site uses, not simply from…

Preserving Next.js cache consistency across instances Several Next.js instances can serve different cached results unless the deployment coordinates their cache and revalidation behavior. A local disk cache…

Protecting a Next.js deployment with a reverse proxy A reverse proxy provides the public connection boundary for a self-hosted Next.js process. It should forward the application correctly while enforcing…

Setting up Next.js image optimization on hosting Next.js image handling depends on the deployment mode and image source configuration. Runtime optimization needs a suitable server environment or a…

Starting a self-hosted Next.js production release A self-hosted Next.js application needs a completed production build, the appropriate runtime files and a supervised process behind the hosting proxy.…

Troubleshooting Next.js server actions after deployment A server-action failure after release can involve mismatched builds, encryption configuration or stale clients. Investigate the deployment state before…

Validating Next.js streamed responses through a proxy A streamed response can send useful page content before all slower work finishes. Proxy or CDN buffering can hide that behavior even when the…