This repository was archived by the owner on Jul 24, 2026. It is now read-only.
build(docs): deploy VitePress docs via platform Dockerfile (Bun -> Caddy) - #166
Merged
Conversation
…ddy) The committed sylphx.toml used `strategy = "auto"`, which cannot build flow's docs as a static site: flow is a Bun *workspace* monorepo with a turbo.json, so the platform's auto buildpack routes it to a node-server build, and the static-frontend detector additionally requires an index.html at the source root (VitePress is markdown, the dist is produced only after build). The result would build the monorepo via turbo and try to run a non-existent node server. Match how every first-party Sylphx app deploys (httphole, sylphx-ai, alpha-foundry all use `strategy = "dockerfile"`): add an explicit Dockerfile that mirrors the platform's canonical bun-static buildpack template — Bun builds the VitePress site, Caddy serves the static output on :3000 — and switch sylphx.toml to the dockerfile strategy with a web service + health path. Verified locally: `docker build` succeeds, the container returns HTTP 200 with real VitePress content at `/`, `/guide/getting-started`, and the `.html` route. Enables the single-source docs deploy on the Sylphx Platform; the duplicate vercel.json is removed separately once the platform deploy is verified live (#165).
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) is meant to deploy on the Sylphx Platform via
sylphx.toml, but the committed manifest usedstrategy = "auto", which cannot build it as a static site. Verified against the platform's actual buildpack source (SylphxAI/platformpackages/core/.../buildpack):bun-staticpath requiresglobs.length === 0;turbo.json, so detection routes tobun-turbo(a node-server build, not static);index.htmlat the source root — VitePress is markdown,docs/.vitepress/dist/index.htmlonly exists after the build;vitepressisn't in the recognized build-tool set.So
strategy = "auto"would build the monorepo via turbo and try to run a node server that doesn't exist → no served docs.Change
Match how every first-party Sylphx app deploys (httphole, sylphx-ai, alpha-foundry all use
strategy = "dockerfile"):Dockerfilemirroring the platform's canonicalbun-staticbuildpack template (ADR-071 v2): Bun builds the VitePress site, Caddy serves the static output on:3000. Base images are digest-pinned to match the platform'sbase-images.json.sylphx.toml→strategy = "dockerfile", awebservice on port 3000, health path/, andwatch_pathsscoped to the docs inputs.No runtime/app code change — deploy config only.
Verification
Built and ran locally:
docker build→ succeeds (VitePress build + static-output probe pass).GET /→ HTTP 200,<title>Sylphx Flow</title>, full VitePress homepage (hero, features, nav, real docs content).GET /guide/getting-started(clean URL) → HTTP 200.GET /guide/getting-started.html→ HTTP 200.Sequencing
This is the enabling change for the single-source docs deploy. The production env tracks
main, so this must land first; then the platform deploy is created + verified live; then the duplicatevercel.jsonis removed in #165.