fix: Keep website bootstrap on Workers after cutover - #63
Merged
Merged
Conversation
Make the website bootstrap follow the tracked Worker hosting mode and fail closed when that configuration is absent. It checks deployment and custom domains before acting, leaves existing Workers untouched, and preserves the explicit Pages path for emergency rollback. Update operating guides to reflect the live Worker domains, release flow, and Pages fallback. Cover first deployment, reruns, and read-only checks in the bootstrap fake Cloudflare tests. Co-authored-by: Codex <noreply@openai.com>
This branch was successfully 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.
TL;DR
The website bootstrap now follows the production Worker configuration. Running it cannot silently recreate a Pages production setup or point the public domains back to Pages after the cutover.
Overview of Changes
The tracked hosting mode selects Worker deployment and custom-domain checks. Bootstrap reads the existing deployment and the apex and
wwwdomain attachments before acting, prompts before a first deployment or new attachment, and fails closed when its hosting configuration is missing. The former Pages path remains available only when explicitly selected for rollback.The fake Cloudflare tests cover first Worker setup, idempotent reruns, read-only doctor checks, and the missing-configuration guard. The deployment and contributor guides now describe the live Worker release path and the retained
pages.devfallback. The repository's fullpnpm checkpasses, and read-only checks against the LVBT Cloudflare account confirm that both public hostnames currently route tolvbt-website.Follow-ups
The Pages deployment remains an emergency fallback. Retiring it requires a separate decision after the Worker release and rollback procedures have operated reliably.