Repository navigation
feat(website): the gateway serves a one-image site and keeps its data plane off the site's route (FD-4683) - #391
Open
williamloo-scale wants to merge 1 commit into
Open
williamloo-scale wants to merge 1 commit into
williamloo-scale wants to merge 1 commit into
Conversation
|
No dependency changes detected. Learn more about Socket for GitHub. 👍 No dependency changes detected in pull request |
williamloo-scale
force-pushed
the
wloo/web-app-contract
branch
from
October 30, 2026 05:23
e4c1cc6 to
f4e254f
Compare
williamloo-scale
force-pushed
the
wloo/web-apps-deploy
branch
from
October 30, 2026 05:23
ad91fbc to
a8c7be7
Compare
… plane off the site's route (FD-4683) A website whose server image serves its pages runs as one container: /website/<name>/ and /svc/<name>/ both reach it, and it's checked at its declared health path. A site's route never forwards its data plane or env card, however the path is spelled, so an agent browsing the site can't read what grades it; agentenv reaches them through /svc/<name>/. A site built on a separate frontend image deploys as before. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
williamloo-scale
force-pushed
the
wloo/web-app-contract
branch
from
October 30, 2026 05:46
f4e254f to
2861aa3
Compare
williamloo-scale
force-pushed
the
wloo/web-apps-deploy
branch
from
October 30, 2026 05:46
a8c7be7 to
22ec1ec
Compare
This branch has not been deployed
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.
The gateway runs a website whose server image serves its pages as one container:
/website/<name>/and/svc/<name>/both reach it, and compose checks it at its declared health path. A site's route now never forwards its data plane or env card (/agentenv/…,/.well-known/agent-env.json, however the path is spelled), so an agent browsing a site can't read what grades it; agentenv still reaches them through/svc/<name>/, as the design'swebsite/v1contract requires. Sites built on a separate frontend image deploy as before.Validation: unit suite passes, with tests for the one-image compose and topology, and the reserved paths through the site route versus
/svc/.🤖 Generated with Claude Code


Confidence Score: 5/5
The PR appears safe to merge; no actionable defects were found.Summary
The gateway now serves websites with one server image while preserving support for separate frontend images.
Diagram
%%{init: {'theme': 'neutral'}}%% flowchart LR Browser[Site request] --> Site["/website/name/path"] Site --> Guard{Reserved path?} Guard -->|Yes| Reject[404] Guard -->|No| Target{Separate frontend?} Target -->|Yes| Frontend[Frontend image] Target -->|No| Server[Server image] Agentenv[agentenv request] --> Service["/svc/name/path"] Service --> ServerReviews (9) · Last reviewed commit: "feat(website): the gateway serves a one-..." · Reviewed by Greptile