Migrate bilingual documentation to Cloudflare cf and Workers - #121
Merged
Merged
Conversation
Deploying pccx with
|
| Latest commit: |
05ebcd8
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://a0e6c23c.pccx.pages.dev |
| Branch Preview URL: | https://codex-cloudflare-cf-20260930.pccx.pages.dev |
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.
Move the existing static output to a Workers asset deployment using pinned cf 1.0.0-beta.5 and its Wrangler build delegate. Keep the existing public hostname and language routes; preview mode verifies the new Worker before the custom-domain cutover. Add locked dependency installation and build/dry-run CI. Existing Pages resources remain available during the cutover.
Validation: the site build and bilingual documentation build passed locally, and both Workers previews were deployed and checked in the browser in English and Korean. The documentation asset rules exclude Sphinx build caches. Production custom-domain and repository-build readbacks are tracked separately from these preview checks.