docs: point the benchmark site at Codeberg Pages

The GitHub Pages deployment died with the deleted repository. The site
now serves from the pages branch at
https://mihaela.codeberg.page/PureYAMLStreaming/ via a git-pages
webhook; the loader fetches the gzipped module and decompresses
client-side, and the same-origin COOP/COEP service worker provides
crossOriginIsolated for the true-streaming benchmark without server
headers. All assets verified serving, module byte count intact.

Closes #2
This commit is contained in:
Mihaela Mihaljevic 2026-07-05 06:48:57 +02:00
parent e1e5d54de7
commit 8d1fcaf020

View File

@ -53,7 +53,11 @@ try parser.parseDocuments(from: url) { document in
Live site:
`https://mihaelamj.github.io/PureYAMLStreaming/`
`https://mihaela.codeberg.page/PureYAMLStreaming/`
Deployed from the `pages` branch: `bash scripts/build-wasm-site.sh`, copy
`WasmSite/` (with the gzipped module, not the raw one) onto that branch, and
push; a repository webhook triggers the git-pages redeploy.
Build the Swift WASI benchmark executable and copy it into the static test site:
@ -89,7 +93,7 @@ loop to model the host-response boundary.
The experimental true-streaming benchmark requires `crossOriginIsolated`,
`SharedArrayBuffer`, `Worker`, and `Atomics.wait`. A same-origin COOP/COEP
service worker enables that mode on localhost and GitHub Pages. In this path,
service worker enables that mode on localhost and Codeberg Pages. In this path,
the main thread reads `fetch().body` with a `ReadableStream` reader, writes each
network chunk into a `SharedArrayBuffer` ring buffer, and a Worker-owned WASI
runtime serves those bytes through a blocking custom stdin `fd_read`. Swift then