This repository was archived by the owner on Jul 24, 2026. It is now read-only.
chore(deploy): remove stale vercel.json — single-source docs deploy via platform - #165
Closed
shtse8 wants to merge 1 commit into
Closed
chore(deploy): remove stale vercel.json — single-source docs deploy via platform#165shtse8 wants to merge 1 commit into
shtse8 wants to merge 1 commit into
Conversation
…phx.toml) flow's docs site was configured to deploy to BOTH Vercel (vercel.json, Git integration on main) and the Sylphx Platform (sylphx.toml [[services]] web, building docs/**). Same site, two deploy definitions = an SSOT violation. The Sylphx Platform manifest is authoritative (we dogfood our own PaaS), so remove the duplicate vercel.json. Before merge: confirm the platform docs deploy is live, then disconnect flow's Vercel project so the docs serve from a single source of truth.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What
flow's docs site (VitePress) had two deploy definitions for the same output:
sylphx.toml→[[services]] webbuildingdocs/**on the Sylphx Platformvercel.json→ Vercel Git integration,docs:build→docs/.vitepress/dist, deploy on push tomainSame site, two pipelines = an SSOT / clean-boundary violation. The Sylphx Platform manifest is authoritative (we dogfood our own PaaS), so this removes the duplicate
vercel.json.Before merging (platform-side, GitOps division of labour)
sylphx.tomlwebservice) is live and serving the docs.No code/runtime change — deploy-config hygiene only. Found during an org-wide deploy-state reconciliation.