Watch

Viktor Vaczi fdc4583288 chore(deploy/site): retire the migration scaffolding, keep the health check

The Vercel -> Cloudflare Pages move is done and the Vercel project is
deleted, so the one-shot scripts have no remaining purpose. Nothing in CI
ever called them — deploy-site.yml runs npm ci / test / build / pages
deploy inline — so this removes 10 files and orphans nothing.

Deleted: 00-baseline (refused to run without x-vercel-id, so permanently
unrunnable), 01-preflight (proved Vercel state and API-token scopes),
07-dns-cutover (the phased cutover; in the end the records were attached
through the dashboard, and the rules/apex phases went unused once we chose
APEX_MODE=serve), 09-detach-vercel (its target project is gone), plus
03-ensure-project, 04-set-secrets, 05-deploy, 06-verify-deploy,
02-verify-local and 99-rollback, all either spent or duplicating CI. Their
lib/cf-api.sh went with them: the survivors use wrangler, so the whole
remaining path needs only `wrangler login` and no zone scopes.

What is kept is the part with ongoing value: lib/parity.sh, the assertion
set that caught five real defects during the migration — the live COOP/COEP
bug on the post's canonical URL, the soft-404 Pages would have introduced,
the cross-site form-POST guard Vercel had been providing for free, the
missing immutable header, and HSTS max-age=0. "Does the page return 200"
catches none of those.

08-verify-prod.sh becomes verify.sh, since the numbered sequence it
belonged to no longer exists. It drops the stamp machinery, the dry-run
plumbing and the Vercel-fallback messaging (there is no fallback now:
recovery is promoting a previous Pages deployment), and gains --skip-dns /
--skip-domains so it can be pointed at a single deployment via PROD_BASE
before promoting it.

The README is rewritten around the four invariants that fail SILENTLY —
never widen _headers to /*, keep both URL forms of the Gerber post, never
delete 404.astro, keep the cross-site form-POST guard — each with the
reason, since the reason is the only thing that stops someone simplifying
them back out.

Verified after: 21 probes, 20 pass, 1 warn (HSTS max-age is 6 months vs
Vercel's 2 years — on, just shorter), 0 fail.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LAmkjM7okPdScp9XLW1JVr

2026-07-27 15:08:56 +02:00

3.9 KiB

Raw Blame History

site

Public-facing marketing/content site for the KiCad WebAssembly project: landing page, blog, and legal pages. Built with Astro 6.

This is a standalone project — it is intentionally decoupled from the /web app monorepo (which is the product itself: React frontend + Fastify backend). It uses npm (not the monorepo's pnpm) and has its own package-lock.json.

What it ships

Static by default: every page is prerendered to HTML and ships zero client JavaScript. A visitor downloads HTML + CSS only — no React/JS bundle.
No adapter and no server bundle: the build emits dist/ only. The single dynamic endpoint, /api/waitlist, ships as a Cloudflare Pages Function from functions/ (see below).

Routes

Route	Source
`/`	`src/pages/index.astro`
`/blog`	`src/pages/blog/index.astro`
`/blog/<id>`	`src/pages/blog/[slug].astro`
`/terms`	`src/pages/terms.astro`
`/privacy`	`src/pages/privacy.astro`
`/cookies`	`src/pages/cookies.astro`

Blog posts are Markdown files in src/content/blog/, validated by the schema in src/content.config.ts. Add a post by dropping a new .md file there with title, description, and pubDate frontmatter.

Local development

Requires Node ≥ 22.12 (Astro 6 requirement).

cd site
npm install
npm run dev        # http://localhost:4321
npm run build      # outputs to dist/ (static only — no adapter)
npm run preview    # serve the production build locally

Dynamic routes

Every page is static. The one server-side endpoint is a Cloudflare Pages Function, not an Astro SSR route:

functions/api/waitlist.ts   ->  POST/OPTIONS/GET  /api/waitlist

Pages maps the functions/ tree to routes by path, and the handlers are named exports (onRequestPost, onRequestOptions, onRequestGet). Config arrives on context.env, not via astro:env/server. public/_routes.json restricts Function invocation to /api/*, so every page and asset stays a plain static request.

To add another endpoint, drop a new file in functions/ — no Astro adapter and no prerender = false involved.

Locally, run the built site the way Pages will serve it (this is the only way to exercise the Function, astro dev does not run functions/):

cp .dev.vars.example .dev.vars   # fill in as needed; gitignored
npm run build
npm run pages:dev                # http://localhost:8788

Deploying

www.pcbjam.com is a Cloudflare Pages project (pcbjam-site), deployed by .github/workflows/deploy-site.yml on every push to main touching site/** — content and blog posts do not wait for a release tag.

push to main (site/**)  ->  npm ci  ->  npm test  ->  astro build
                        ->  wrangler pages deploy  ->  www.pcbjam.com

Two things live outside the repo and are set once:

Secrets — wrangler pages secret put <NAME> --project-name pcbjam-site for RESEND_API_KEY, RESEND_SEGMENT_ID, WAITLIST_FROM_EMAIL. WAITLIST_ALLOWED_ORIGINS is deliberately unset; it keeps the in-code default.
The custom domain — attached to the Pages project (there is no wrangler pages domain subcommand). The apex pcbjam.com 308s to www via a Cloudflare Redirect Rule.

Response headers come from public/_headers (copied verbatim into dist/), which carries the COOP/COEP rules the embedded Gerber viewer needs. Do not widen them to /* — the landing page must stay un-isolated so the YouTube hero embed loads.

One-time setup, the invariants that fail silently if changed, and the health check (deploy/site/verify.sh) are in ../deploy/site/README.md.

3.9 KiB Raw Blame History