[reecelikesramen]

Needs #400 (merged): the example Workers use main = "src/entry.py", which #400 teaches pywire build to keep. The Workers themselves, their routes and DNS are created by pywire/pywire.dev#18.

Before: none of the examples ran anywhere public.

After: demo.pywire.dev has a landing page listing the demos, the form builder at demo.pywire.dev/form-builder/, and the stateless demo at demo.pywire.dev/edge-stateless/. Every push to main that touches those examples or pywire itself redeploys them, so the demos always run main.

Each example deploys from its own folder, the same way a create-pywire-app project would. There is no staging step. Examples aren't released, so release-please isn't involved.

How:

• Each example has a committed wrangler.toml (Worker pywire-demo-<name>, main = "src/entry.py", PYWIRE_BASE_PATH=/<name>) with code and vars only. Terraform in pywire.dev creates the Worker and its routes, the way it creates the docs Pages project.
• pywire[cli] sits in each example's dev group, so the Worker bundle holds only runtime dependencies.
• .github/workflows/deploy-examples.yml runs on pushes to main (paths filtered) and by hand. It deploys examples/demo-site with wrangler. For each example it builds the client bundle, runs uv run pywire build --platform cloudflare-edge, then uv run --with workers-py pywrangler deploy.
• UV_NO_EDITABLE=1 makes pywrangler vendor a real copy of the workspace's pywire rather than an editable link, so the demos run main's source.
• The form builder gets CLIENT_IP_HEADER=cf-connecting-ip, which Cloudflare sets itself.
• realtime waits for the shared Durable Object target (fix(pywire-templates): run Cloudflare apps in regional Durable Objects #393). taskboard needs a database, so it's left out.

Order:

1. Merge pywire.dev#18 and run Infra apply. That creates the Workers, routes and DNS.
2. Reece gives this repo's CLOUDFLARE_API_TOKEN the account-level Workers permission at Editor.
3. Merge this. The first run uploads the code.
4. Reece sets the Worker secrets: PYWIRE_SECRET_KEY on both example Workers, plus GROQ_API_KEY and TYPESAFE_API_KEY on pywire-demo-form-builder (commands in examples/README.md). The examples return errors until then.

Worth knowing: the form builder's rate limiter keeps its counts in memory. On Workers each isolate has its own memory, so a visitor can get more than 10 builds per 10 minutes. The out-of-usage message still covers the case where the keys run dry.

Tests: in examples/form-builder I ran the build and UV_NO_EDITABLE=1 uv run --with workers-py pywrangler dev in local workerd. The page, CSS and client loaded under /form-builder/, stateless POSTs returned 200, and a build with a fake key showed the out-of-usage message. A dry-run upload is 2.5 MB gzipped. The Examples check passes.

🤖 Generated with Claude Code