Repository navigation
feat(site,docs): the demo is answering again, so point at it again - #45
Merged
Merged
Conversation
The demo gateways were redeployed today — fold-demo-tasks, fold-demo and fold-enterprise are back on tasks/demo/enterprise.fold.run, all three healthy, with the walkthrough verified end to end against the running gateway (three namespaces federate, a minted task polls from a session that never saw it minted). This restores what #44 removed once the thing it pointed at was gone: the homepage demo section and its styles, the nav and footer demo links, the docs walkthrough and its sidebar entry, and the benchmarks bullet warning against benchmarking the demo. The status page stays gone, and the uptime worker stays undeployed. It watched the fold cloud as well as the demo, and the fold cloud is still down — every one of api, broker, mcp and console answers 522 — so a status page would come up mostly red and argue against the demo the rest of this commit is restoring. The two sentences that sent readers to /status for live state are dropped rather than left dangling; the page comes back when there is a cloud for it to report on. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This was referenced Aug 26, 2026
blakebauman
added a commit
that referenced
this pull request
Aug 26, 2026
enterprise.fold.run has been deployed and healthy since the redeploy in #45, and nothing anywhere pointed at it — a finished gateway with tenants, budgets, deny-by-default policy and audit configured, that no reader could find. This links it beside the demo, where the argument lands: it is the same binary over a byte-identical upstream set, with the governance on. homepage a governed block closing the #demo section, with the console and /mcp in a route rail marked "sign-in required" footer "Governed gateway" in the Product column docs a "same federation, governed" section in the walkthrough Every claim is checked against the running config rather than written from memory: both gateways federate the identical three upstreams (same ids, urls and namespaces), auth.mode is required, policy is deny-by-default, acme gets 5,000 calls/day at 120 req/min, globex 1,000 at 60 and no GitMCP at all. Both curl examples in the docs were run verbatim and produce the documented output — the 401 carries the RFC 9728 challenge, and the metadata names oauth.work as the issuer. It is a separate deployment because auth.mode is gateway-wide: governing the demo would take away the copy-pasteable thing the demo exists to be. The new copy says so rather than leaving two gateways unexplained. Deliberately not referenced: /demo-token, which is 503 because deleting the Worker in the teardown destroyed its four oauth.work client-credentials secrets. Nothing shipped here depends on it, so this points only at paths that answer today — the console (which reaches a real login flow; the SPA client is registered) and the 401 discovery path. Restoring those secrets is what would let the walkthrough add a copy-paste token and go behind the wall. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reverses #44 for the demo half only. That PR removed the pointers because the thing they pointed at had been deleted in the 2026-08-18 teardown; the gateways are redeployed, so the pointers come back.
Redeployed first
All three workers had been deleted from the account, not idled, so these were fresh creates — new Durable Object namespaces and new container applications.
fold-demo-taskslite, max 1fold-demobasic, max 1fold-enterprisebasic, max 1Restored
#demosection, its three upstream cards, and its stylesdocs.fold.run/try-the-demo/and its sidebar entryDeliberately not restored
The
/status/page, the footer status badge and its uptime fetch, andfold-uptimestays undeployed.The monitor watched the fold cloud as well as the demo, and the fold cloud is still down —
api,broker,mcpandconsoleall answer 522. A status page fed by that monitor would come up mostly red and argue against the demo sitting next to it, which is the same failure mode #44 was fixing, pointed the other way. It comes back when there is a cloud for it to report on.The two sentences that sent readers to
/statusfor live state are dropped rather than left dangling: one in the homepage demo intro, one in the walkthrough's opening line.Verification
The walkthrough was checked against the running gateway rather than assumed from the restored text:
tools/listreturns 8 tools acrosscfdocs(2),git(5),jobs(1), with norun.fold/partialFailure— all three upstreams federatejobs__start_jobmints a task into the result's_meta, origin-taggedrun.fold/upstream: demo-taskstasks/getfrom a brand-new session that never saw it minted, which is the cross-session affinity claim the page makesBuild, typecheck and lint pass. The single lint warning is pre-existing on a clean tree.
Follow-up, not in this PR
Deleting
fold-enterprisetook its secrets with it, soenterprise.fold.run/demo-tokenreturns503 demo token vending is not configured yet. The four oauth.work client-credentials values need restoring withwrangler secret put. Nothing on the site links to that endpoint, so it does not block this.🤖 Generated with Claude Code