Files
zeekay 7d781bc1eb build: serve ui.hanzo.ai from our own stack
The site was on Cloudflare Pages as a direct upload — no git connection,
last deployed 2026-03-28 — while a GitHub Pages workflow ran on every
push against a repo that has Pages disabled (the API 404s). Two deploy
paths, neither of which shipped what main said.

One way now: a Dockerfile builds the static export and serves it with
ghcr.io/hanzoai/static, exactly like every other Hanzo static site, on
our own runners and our own ingress.

Along the way, drop what those two vendors left behind:
- output:'export' was gated on GITHUB_ACTIONS || CF_PAGES, so a build
  anywhere else silently produced no export at all. The site is a static
  export wherever it is built.
- basePath pointed at a '/react-sdk' GitHub Pages subdirectory that is
  not this project.
- highlight-code keyed off GITHUB_ACTIONS to pick server vs client
  highlighting; it means 'is this a production export', so it says that.
- pages/api/components returned a JSON blob and 404s in production,
  because a static export cannot serve an API route. The live index is
  the generated /api/registry/components.json.
2026-07-25 12:46:18 -07:00
..