Skip to content

feat(website): show the UI demo as a recording only - #418

Merged
kvlonge merged 1 commit into
mainfrom
feat/demo-recording-only
Nov 14, 2026
Merged

kvlonge merged 1 commit into
mainfrom
feat/demo-recording-only

Conversation

@kvlonge

@kvlonge kvlonge commented Nov 14, 2026

Copy link
Copy Markdown
Contributor

Why

The live in-browser ClickHouse mode made the UI demo at sqltide.io/demo awkward to use. The demo should show the recording only, as it did before the engine.

Changes

  • The demo loads the recording directly. Every GET answers from recordings.json, writes return the read-only message, and unrecorded GETs fail loudly. The banner reads "UI demo with recorded example data. It is read-only."
  • Removed the engine mode and everything only it used:
    • the live banner, the "Live in this tab" panel and Start over;
    • the prepared story (prepared.json) and the warehouse readers;
    • the engine's build steps, isolation headers, chdb-wasm, the test server, and its CI job;
    • the engine-only tests, the warehouse-health capacity override, and the faster polling.
  • prepare-demo.mjs is record-demo.mjs again. It records pages only, on its own ports and Docker project. The recording was refreshed with sqt 0.70.1 from PyPI.
  • Release PRs still stamp the version into the recorded /api/status. The prepared.json entry is gone from the release config and the release-PR allowlists.
  • README, quickstart and UI overview describe the demo as recorded and read-only.
  • sqt dev's deployment rollback stays.

Verification

  • svelte-check clean; UI vitest 211/211; fensu 0 faults.
  • Website: build, link check (130 pages, 0 broken), check_production.py, and Playwright 10/10, including every recorded demo page.
  • record-demo.mjs run end to end with Docker: 29 pages and 160 responses, the same as the committed recording.
  • Independent review: no blockers.

The in-browser ClickHouse mode made the demo awkward to use. The demo
now loads the recording directly: every GET answers from it and writes
return the read-only message, as before the engine.

Removes the live engine, its banner and panel, Start over, the prepared
story and its CI job, the warehouse readers, the engine's build steps,
headers and dependency, and the tests that covered only them. The
recorder goes back to recording pages only, and release PRs still stamp
the version into the recorded status.
@kvlonge
kvlonge enabled auto-merge (squash) November 14, 2026 18:14
@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying sqltide with  Cloudflare Pages  Cloudflare Pages

Latest commit: 56fd73d
Status: ✅  Deploy successful!
Preview URL: https://d8e307dd.sqltide.pages.dev
Branch Preview URL: https://feat-demo-recording-only.sqltide.pages.dev

View logs

@kvlonge
kvlonge merged commit c8b02fc into main Nov 14, 2026
11 checks passed
@kvlonge
kvlonge deleted the feat/demo-recording-only branch November 14, 2026 18:37
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.

1 participant