The best way to control Claude Code, Codex and more from any computer or phone
| 1 | # Shorty, chapter by chapter |
| 2 | |
| 3 | Each folder is the complete app at the end of one chapter of the talk |
| 4 | (see `../CONTENT.md`). Consecutive folders differ by exactly that |
| 5 | chapter's change, so the recording types the diff between them. |
| 6 | |
| 7 | | Chapter | What it adds | |
| 8 | | --- | --- | |
| 9 | | `00-website` | `Cloudflare.Website.Vite` dashboard shell | |
| 10 | | `01-api` | Effectful Worker serving an `HttpApi`; typed client in the dashboard | |
| 11 | | `02-d1` | D1 database with migrations; redirects | |
| 12 | | `03-tests` | `test/api.test.ts`: deploy → assert → destroy | |
| 13 | | `04-durable-objects` | `LinkRoom` Durable Object, hibernatable WebSockets, live counts | |
| 14 | | `05-queues` | `Clicks` queue: redirects enqueue, a consumer counts in batches | |
| 15 | | `06-layers-neon` | `Links` service + `LinksSql`; storage Layers for D1 and Neon via Hyperdrive | |
| 16 | | `07-telemetry` | Spans, Axiom datasets and ingest token, `Axiom.Telemetry` | |
| 17 | | `08-dashboard` | `Axiom.Dashboard` as code | |
| 18 | |
| 19 | Run a chapter from its folder, with the demo's binaries on `PATH`: |
| 20 | |
| 21 | ```sh |
| 22 | export PATH="$PWD/../../node_modules/.bin:$PATH" ALCHEMY_PROFILE=testing |
| 23 | alchemy dev # API on localhost:1337, dashboard on localhost:5173 |
| 24 | pnpm test # deploys test_$USER, runs the tests, destroys it |
| 25 | ``` |
| 26 | |
| 27 | Dependencies come from `demos/effect-prezzy/package.json`. Type-check a |
| 28 | chapter from the repo root with `pnpm exec tsc -b demos/effect-prezzy/chapters/<folder>`. |