Skip to content

DEPLOY.md

Latest commit

 

History

History
57 lines (42 loc) · 2.53 KB

DEPLOY.md

File metadata and controls

57 lines (42 loc) · 2.53 KB
Raw

Deploying The Crosswalk

The site is pure static files in public/ — no build step. Cloudflare Pages serves that directory. Everything below is wired; the one thing that is yours, not mine, is the publish itself — it needs your Cloudflare account and auth, which I never touch.

The discipline: bracket every deploy

  • Before: node crosswalk-gate.js proves the SOURCE is correct (238 checks — palette, contrast, links, the Stable's own integrity). Green or it does not go out.
  • Deploy: push the public/ folder to Cloudflare Pages.
  • After: node verify-live-crosswalk.js <url> fetches the LIVE bytes and re-checks that the deploy actually carried the source (reachable, right titles, no stale legacy name, the door walkable, every link live). This catches a stale cache or a host pointed at an old build — the thing a source gate cannot see.

One-time setup (you, once)

You already deploy another project to Cloudflare Pages, so the account exists. Create the project (dashboard, or CLI):

npx wrangler login                        # opens your browser; your auth, not stored here
npx wrangler pages project create the-crosswalk --production-branch main

Deploy (the repeatable command)

node crosswalk-gate.js                     # must print GREEN first
npx wrangler pages deploy public --project-name the-crosswalk

Wrangler prints the live URL (e.g. https://the-crosswalk.pages.dev). Then verify it landed:

node verify-live-crosswalk.js https://the-crosswalk.pages.dev

GREEN means the live site matches the source and the door is walkable. RED almost always means a stale cache — wait a moment and re-run, or purge the cache in the Pages dashboard.

Alternative: git-based deploy (more robust for ongoing)

wrangler pages deploy is a direct upload — fastest to first-live. For ongoing work, connecting a GitHub repo to the Pages project (dashboard → Pages → connect to Git, build output dir = public, no build command) means every push auto-deploys. That step needs your GitHub auth, so it is also yours to click.

Notes

  • Only public/ ships. stable/ and witness-suite/ stay in the repo but are never served — the human branch does not publish a horse.
  • No secrets in this repo. Auth is your wrangler login session or a CLOUDFLARE_API_TOKEN you set in your own environment. Nothing here contains a credential.
  • The real test is not the deploy. It is a newcomer using the live door while you watch. Green here just means the door is reachable for that test.