Skip to content
alkemist / an open workbench

Hosting and branch previews

A Git-backed Cloudflare Pages workflow for the Alkemist demo and documentation.

The site’s production address is alkemist.alkem.dev. Cloudflare Pages builds the site from the alkemdev/alkemist GitHub repository.

Branch behavior

  • Pushes to main publish the production website.
  • Pushes to other repository branches create preview deployments.
  • Each deployment has an immutable URL; Cloudflare also provides a branch alias that follows that branch’s latest successful deployment.
  • Preview pages include a visible development banner and no-index metadata. Cloudflare also supplies its preview indexing controls.

Preview URLs are public links, not an authentication boundary. Only place content intended for publication in a branch you deploy.

The Cloudflare Git integration builds directly from GitHub. There is no separate upload workflow and no Cloudflare deployment token stored in this repository or its build environment. PR comments are disabled.

Build contract

npm ci && npm run verify

The build runs at the repository root and serves apps/site/dist. Node is pinned to 24.20.0. A failed verification command prevents deployment.

/build.json identifies the source revision, branch, environment, and build time. This lets us verify that a production or preview URL serves the expected commit.

Managed configuration

The initial production deployment and two successive pushes to preview/deployment-check were verified on September 8, 2026. The stable preview advanced to its second source revision while production stayed unchanged. HTTPS checks covered the deployed commit, branch/environment, documentation routes, preview no-index behavior, headers, and 404 responses.

Run the same live checks with an expected full commit and branch:

node scripts/check-deployment.mjs https://alkemist.alkem.dev <full-commit> main

The deployment settings are recorded in infra/cloudflare.json. npm run cloudflare:status reads the remote state. npm run cloudflare:setup reconciles the expected Pages project and domain using an operator-provided Cloudflare token; it checks repository identity and refuses to replace an unrelated DNS record.

Cloudflare documents GitHub integration and preview deployment behavior.