docs: correct backend/ claims — ci.forkhorizon.com is the real production backend#80
Merged
Merged
Conversation
…tion backend Verified conclusively: ci.forkhorizon.com resolves to the production VPS and nginx proxies it (with the 3 other private dashboards) to the single Node process from ForkHorizon/WebSite's src/products/ci-scope/backend.ts. That backend already implements infra-vs-test failure classification and auto-rerun (per WebSite's own project memory). It also matches the broker's actual wire protocol: CIQueueSettingsStore.swift and LocalBrokerLaunchAgent.swift call /api/ci/local/heartbeat, which is a WebSite ci-scope route, not anything in this repo's backend/. The Python backend/ folder here implements a different, incompatible protocol (/github/webhook, its own SQLite store) and was never deployed — its own README still has the your-backend.example.com placeholder everywhere, and there is no nginx route to it on the production VPS. README previously called this folder 'the production path', which was wrong. Reframed as a parked prototype and pointed Server mode config at the real production backend.
Daliys
marked this pull request as ready for review
July 25, 2026 18:58
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
1 participant
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.
Why
README called
backend/(a standalone Python/FastAPI GitHub-App-webhook receiver in this repo) "the production path." I verified that's not true:ci.forkhorizon.comresolves to the production VPS; nginx proxies it (with the other 3 private dashboards) to a single Node process — that'sForkHorizon/WebSite'ssrc/products/ci-scope/backend.ts, not anything in this repo.CIQueueSettingsStore.swift,LocalBrokerLaunchAgent.swift) hit/api/ci/local/heartbeat— a WebSiteci-scoperoute, not this repo'sbackend/(which exposes/github/webhookinstead, a different, incompatible shape).backend/'s own internal README still has the placeholder domainyour-backend.example.comeverywhere, and there's no nginx route to it anywhere on the production VPS.What changed
CI_SCOPE_BACKEND_URL) athttps://ci.forkhorizon.com.backend/is a separate, earlier, undeployed prototype — not a second production path — until it's either wired up for real or removed.This doesn't touch
backend/itself, just the docs claiming it's live. Whether to delete/revivebackend/is a separate decision.Left as a draft — not merging myself, surfacing for review.