Repository navigation
Move docs hosting to Vercel - #328
Merged
Merged
Conversation
- sent from alixander's Codex
- sent from alixander's Codex
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.
Human
AI
Move the docs site to the sponsored D2 Vercel team. Vercel builds the static Docusaurus site with pinned Yarn, preserves installer and Plausible proxies, and serves hashed assets with immutable caching. All five existing CI checks remain; the AWS deploy job is removed. The independent daily job uses the unique display name
daily-ciso production checks cannot mistake it for the main build.Reindex Algolia after successful production deployments for this project, with a manual production recrawl for cutover and rollback. Document setup, deployment checks and rollback.
Validation: the Node 24/Yarn 1.22.22 production build passed (1,464 files), both push and PR CI checks passed, and the changed configuration/workflows passed validation. After merge, the Git-sourced production deployment at master 5530a5e passed all five CI checks before production alias assignment. Both custom domains now resolve to Vercel with valid TLS. Public probes verified pages, both slash forms, canonical metadata, generated redirects, custom 404, sitemap, hashed assets, installer byte parity, Plausible script parity and POST forwarding, and Algolia configuration. Automatic and post-cutover manual Algolia reindex requests succeeded.
Project d2-docs is connected to GitHub master with Standard builds and paid concurrency disabled. Route 53 cutover is INSYNC; playground and all ten legacy redirects remain healthy.