Skip to content

KBVE CDN — cdn.kbve.com and kbve.com/_kbve

What it is

An axum service in the kbve namespace with two jobs:

  • /_kbve/<name> — the site’s content-hashed bundles. A hashed name never changes its bytes, so each file is fetched from kbve-web once and kept on an append-only volume for good. Every minute it copies whatever the live site release lists in /_kbve/.release; a name it has not seen is fetched from the site on first request. /_kbve/fonts/<name> is held the same way. Responses are immutable for a year.
  • /assets/<path> — the shared tree in services/cdn/assets, baked into the image, for images that the README, social cards and other sites read.

It is pulled, not pushed: no build uploads to it, so nothing upstream holds a credential for it, and no other workload mounts its volume.

Why

Pages kbve-web does not serve itself — the forum’s and profile’s, rendered from a pinned site release — link that release’s hashed bundles. While those bundles only lived inside the kbve-web image, a site release either carried them forward or broke those pages’ styling. Kept here, they outlive any number of site releases, and other sites can lean on the same store.

Routing

cdn.kbve.com reaches it directly, and the kbve.com gateway sends kbve.com/_kbve to it as well. That path stays on the site’s origin on purpose: the chat’s SharedWorkers load from /_kbve, and a browser starts a SharedWorker only from the page’s own origin.

Storage

A Longhorn ReadWriteMany volume shared by both replicas. Files are written beside their final name and renamed into place, so a reader never sees half a file, and two replicas fetching the same name write the same bytes.

Discuss on the forum

Questions, fixes and notes on this page live in the KBVE forum.