diff --git a/apps/demo/Dockerfile b/apps/demo/Dockerfile index 6072237..739df58 100644 --- a/apps/demo/Dockerfile +++ b/apps/demo/Dockerfile @@ -3,7 +3,7 @@ # image until `pnpm --filter @fold-run/demo run deploy` runs. Update # expectVersion in apps/uptime/src/index.ts in the same commit — CI enforces # it, and the monitor then catches a pin that shipped without a deploy. -FROM ghcr.io/fold-run/fold:v1.13.0 +FROM ghcr.io/fold-run/fold:v1.14.0 # Distroless ENTRYPOINT is ["/fold"]; bind beyond loopback for the container # network. Config arrives via FOLD_CONFIG (set by the Container class). CMD ["--host", "0.0.0.0", "--port", "8080", "--log-format", "json"] diff --git a/apps/docs/src/content/docs/conformance.md b/apps/docs/src/content/docs/conformance.md index 8bfb120..b76994e 100644 --- a/apps/docs/src/content/docs/conformance.md +++ b/apps/docs/src/content/docs/conformance.md @@ -20,7 +20,7 @@ servers back to the originating client. **The receipt is one click away**, because a conformance claim you have to take on faith isn't one: the -[`conformance` job from the v1.13.0 release run](https://github.com/fold-run/fold/actions/runs/31833840044/job/94875553255), +[`conformance` job from the v1.14.0 release run](https://github.com/fold-run/fold/actions/runs/31889072914/job/95022525328), and [every green run on `main`](https://github.com/fold-run/fold/actions/workflows/ci.yml?query=branch%3Amain+is%3Asuccess). diff --git a/apps/docs/src/content/docs/try-the-demo.md b/apps/docs/src/content/docs/try-the-demo.md index 6a52b0f..f1b4651 100644 --- a/apps/docs/src/content/docs/try-the-demo.md +++ b/apps/docs/src/content/docs/try-the-demo.md @@ -95,7 +95,7 @@ GitMCP speaks the 2025-era session handshake. fold — built on the official Go ## 5. Watch it in the console -Open **[demo.fold.run/console](https://demo.fold.run/console/)** — the read-only [fold console](/console/), enabled in the demo's config. The dashboard shows the three upstreams, their breaker state, and the deployment facts live, and **[the map view](https://demo.fold.run/console/#/upstreams?view=map)** draws the federation itself: one gateway node fanning out to cfdocs, git, and jobs, each route carrying that upstream's current breaker state. It's generated from `/api/federation`, so it's this demo's real topology, not a picture of one. The test console is a plain MCP client against the same `/mcp` endpoint you've been curling, governed and audited like any other caller. +Open **[demo.fold.run/console](https://demo.fold.run/console/)** — the read-only [fold console](/console/), enabled in the demo's config. The upstreams table shows a row per upstream — namespace, source, auth, connected, breaker, latency — and **[the map view](https://demo.fold.run/console/#/upstreams?view=map)** draws the federation itself: one gateway node fanning out to cfdocs, git, and jobs, each route labelled with the latency that upstream is answering in, over a footer reading `3 of 3 connected · every route crosses auth, policy and audit`. It's generated from `/api/federation`, so it's this demo's real topology, not a picture of one. The test console is a plain MCP client against the same `/mcp` endpoint you've been curling, governed and audited like any other caller. ## The same federation, governed diff --git a/apps/enterprise/Dockerfile b/apps/enterprise/Dockerfile index 9402d6c..ed7d645 100644 --- a/apps/enterprise/Dockerfile +++ b/apps/enterprise/Dockerfile @@ -4,7 +4,7 @@ # step with apps/demo/Dockerfile, and update expectVersion in # apps/uptime/src/index.ts in the same commit — CI enforces it, and the monitor # then catches a pin that shipped without a deploy. -FROM ghcr.io/fold-run/fold:v1.13.0 +FROM ghcr.io/fold-run/fold:v1.14.0 # Distroless ENTRYPOINT is ["/fold"]; bind beyond loopback for the container # network. Config arrives via FOLD_CONFIG (set by the Container class). CMD ["--host", "0.0.0.0", "--port", "8080", "--log-format", "json"] diff --git a/apps/site/src/pages/index.astro b/apps/site/src/pages/index.astro index 6e4150d..491b2d1 100644 --- a/apps/site/src/pages/index.astro +++ b/apps/site/src/pages/index.astro @@ -210,11 +210,12 @@ const jsonld = {
The console ships inside the binary and needs no client. Open it and you are reading the - running federation: live latency and breaker state per upstream, the policy in effect, the - rate limit. Its test console calls the same endpoint everything else does. The topology - at the top of this page is drawn by hand; the console draws its own from the federation it is serving. + > from the federation it is serving, each route labelled with the latency it is answering + in.