Deployment — Cloudflare

This registry is published as a static docs site on Cloudflare. The repo holds only source (*.md, build.mjs); the rendered site is generated into public/ at deploy time, so public/ is git-ignored and never committed. There are no secrets and no database.

How it deploys (current setup — no dashboard build settings needed)

The Cloudflare project deploys by running npx wrangler deploy. wrangler.jsonc makes that one command do everything:

  • build.command = npm run build → renders every .md into ./public
  • assets.directory = ./public → serves those files as static assets

So on each push, Cloudflare installs dependencies and runs npx wrangler deploy, which builds the site and uploads it. Nothing else to configure — no build command / output directory to set in the dashboard, and no committed public/.

Updating the docs

Edit any .md file and push. Cloudflare runs npx wrangler deploy → npm run build → redeploys. Don't commit public/ (it's generated output, git-ignored).

Deploy the latest commit — don't use "Retry." In the Cloudflare dashboard, Retry deployment re-runs the exact commit that deployment was created for, so it never picks up newer commits. To ship the latest main, push a commit (auto-deploys) or create a new deployment of main.

Local preview

npm install
npm run build       # renders ./public
npm run dev         # wrangler dev — serves the built assets locally

Branch discipline

  • Don't push directly to main — it auto-deploys production.
  • Feature branch → PR → merge (only when requested) → delete the branch afterwards.

Alternative — Cloudflare Pages

If you ever move to a Pages project instead of a Worker: create it via Workers & Pages → Create → Pages → Connect to Git, set Framework = None, Build command = npm run build, Output directory = public (no wrangler.jsonc needed for Pages). Both approaches build the same public/ from the Markdown; pick one.