Server and deployment — Nexis documentation

Deploy the final artifacts

Nexis v1.3.3 supports the standard lifecycle pnpm dev, pnpm build, then pnpm start. The build emits client HTML, server modules, lazy chunks, runtime assets, manifest, sitemap, feeds, redirects, public assets, and any required media output.

Choose the adapter intentionally

Use createServer or the standard pnpm start command for Node hosting. Use a Fetch-native Deno/Cloudflare adapter where that runtime is the deployment target.

Make operational policy explicit

Trust forwarded headers only behind a controlled proxy, set cache policy per render mode, expose health checks, bound bodies, and support graceful shutdown.

PRACTICAL LABS

Run this capability.

Each example states the observable output, the boundary that remains your responsibility, and the check that proves the result.

Build the production artifact

Shell

pnpm install --frozen-lockfile
NEXIS_SITE_ORIGIN=https://app.example.com pnpm typecheck
NEXIS_SITE_ORIGIN=https://app.example.com pnpm check
NEXIS_SITE_ORIGIN=https://app.example.com pnpm build
pnpm start

OUTPUT: The final artifact is built with its production origin and can be served directly.
BOUNDARY: Enable proxy trust only behind a proxy that removes client-controlled forwarded headers.
PROVE IT: Check redirects, 404, 405, HEAD, cache headers, and health behavior on the production server.

VERIFICATION

Prove the contract.

Test fresh deploy behavior, redirects, 404/405/HEAD responses, proxy headers, cache headers, health endpoint, and shutdown.