Deployment

Resux supports Node, Docker, and Nitro deployment flows.

Production build

npm run build

A full production build creates:

.resux/     lower-level Resux server/client build output
.output/    Nitro production server output

Run it:

node .output/server/index.mjs

The generated starter maps this to:

npm run start

Node server

npm install
npm run build
PORT=3000 npm run start

Docker files

Generate Docker deployment files:

resux deploy . --preset docker

Overwrite existing files:

resux deploy . --preset docker --force

Build and run:

docker build -t resux-app .
docker run --rm -p 3000:3000 resux-app

Nitro preset

Generate Nitro helper files:

resux deploy . --preset nitro

The Nitro preset writes:

nitro.config.ts
.resux-nitro/handler.ts

The generated handler wraps createResuxNodeHandler() from resuxjs/node.

Security headers

Production serving enables default hardening headers, including examples such as:

• x-content-type-options
• referrer-policy
• x-frame-options
• cross-origin-opener-policy
• restrictive permissions-policy

Disable them only when your host or reverse proxy owns those headers:

resux start . --no-security-headers

Health checks

Use:

/__resux/health

Inspect in CI

resux inspect . --json > resux-manifest-summary.json

The inspect output helps capture routes, server handlers, route rules, features, and diagnostics during deployment.