Deployment & self-hosting

Deploy generated WOWW sites to static hosting or package your own runtime integration.

Recommended deployment modes

Static hostingBest for generated pages, assets and docs sites. Supports Cloudflare Pages, Vercel and Netlify.

Custom Node runtimeUse your own Node server for SSR/API routes implemented by your application.

Build and publish

npm ci
npm run build
node dist/cli.js build
# publish ./dist

Docker pattern for static output

FROM node:22-alpine AS build
WORKDIR /app
COPY package*.json ./
RUN npm ci
COPY . .
RUN npm run build && node dist/cli.js build

FROM nginx:alpine
COPY --from=build /app/dist /usr/share/nginx/html
EXPOSE 80

This is a generic container pattern for the generated static site, not an official WOWW application server image.

Kubernetes and bare-metal

Deploy the static container behind an ingress or serve the output with Nginx/Caddy on Linux. WOWW does not currently publish an official Helm chart, a woww/core image, or a systemd application daemon.

Infrastructure sizing

For static sites, build concurrency and image processing determine most resource needs. A full Git hosting platform additionally requires sizing database IOPS, repository storage, object storage, search, cache and runner capacity using real traffic and repository measurements.

Scope note: WOWW 0.2.0 is a framework package. Hosted Git collaboration, account management, Copilot plans, hosted runners, public REST/GraphQL services and a woww/core server image are not included. The related guidance below is architecture or integration advice, not a claim that those services are live.

← Documentation home