Skip to content

[M11] Render static site deploy (M11.10) - #100

Merged
ssoufii merged 1 commit into
mainfrom
auto/m11.10-render-deploy
Nov 17, 2026
Merged

ssoufii merged 1 commit into
mainfrom
auto/m11.10-render-deploy

Conversation

@ssoufii

@ssoufii ssoufii commented Nov 17, 2026

Copy link
Copy Markdown
Owner

The demo is ready to deploy on Render as a static site, and Milestone 11 is complete.

Changes

  • render.yaml (Blueprint): a static runtime, rootDir: web, npm ci && npm run build, publishing dist. Caching: Cache-Control: public, max-age=31536000, immutable on /assets/* (Vite-hashed), and no-cache on /index.html, / and /engine/*. The engine source is copied in unhashed, and the page claims to run this commit's engine. NODE_VERSION=22 matches CI. A buildFilter redeploys on web/**, src/ledgerlog/** and README.md, because the build copies the engine source and parses the README's bench tables.
  • web/tests/deploy.spec.ts:
    • It checks the blueprint's fields.
    • It runs a full visit and fails on any request to an origin other than the site itself and Fontshare. The visit boots Pyodide, does a put and a flush, runs a crash scenario, scrolls to the end and waits for the network to go idle.
  • README: a new "Live demo" section (how to deploy on Render, and how to run the site locally), and the Status line now covers M11.
  • docs/ROADMAP.md: the remaining Milestone 11 boxes are ticked.

Acceptance criteria

  • render.yaml defines the static site: root web, build npm ci && npm run build, publish dist, long cache for hashed assets, no-cache for index.html
  • The full Playwright suite passes against vite preview of the production build; a test asserts no requests to other origins apart from the font provider
  • README "Live demo" section: deploy on Render (connect the repo, Render reads render.yaml) and run locally
  • docs/ROADMAP.md ticks Milestone 11

Verified locally (macOS)

  • node scripts/bench-data.mjs --check: bench.json still matches the README after the README edit.
  • Playwright: 134 passed. The 2 failures are the existing console.spec.ts keyboard test, which presses Control+A. That doesn't select all on macOS, so it is a Mac-only failure; it passes on Linux CI.
  • pytest: 1304 passed, 6 skipped. Ruff is clean.

Connecting the Render account is for the owner, as the story says.

Closes #88

🤖 Generated with Claude Code

https://claude.ai/code/session_01QWNkuQ7vhXw8ijQ3q3NZDG

Story M11.10. render.yaml publishes web/dist as a static site with immutable
caching for hashed assets and no-cache for the page and the engine source,
and redeploys on changes to web/, src/ledgerlog/ or the README.
tests/deploy.spec.ts checks the blueprint and fails if a full visit contacts
any origin but the site itself and Fontshare. The roadmap ticks Milestone 11.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QWNkuQ7vhXw8ijQ3q3NZDG
@ssoufii
ssoufii merged commit e7a9c96 into main Nov 17, 2026
16 of 18 checks passed
@ssoufii
ssoufii deleted the auto/m11.10-render-deploy branch November 17, 2026 07:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[M11] Render static site deploy (M11.10)

1 participant