Solution skill
Where Zeabur deploys build output for a Vitepress project
Complete solution
Shows how to fix where Zeabur deploys build output for a Vitepress project. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
The reporter expected the default build command to deploy the dist folder at the project root and wanted to configure the output path. (Issue filed in Chinese; paraphrased.) At the time, Zeabur did not let users configure the build output path at all, per maintainer yuaanlin.
Steps
- Issue zeabur/zeabur#41 (closed, 5 comments): Where does Zeabur put the build output for a static deploy? The reporter expected the default build command to deploy the dist folder at the project root and wanted to configure the output path. (Issue filed in Chinese; paraphrased.)
- At the time, Zeabur did not let users configure the build output path at all, per maintainer yuaanlin. For Vitepress projects specifically, the officially supported setup is: Zeabur runs the build or docs:build command, then serves the files from docs/.vitepress/dist as static output. So if your Vitepress deploy serves nothing, make sure your build script is named build or docs:build and your output lands in docs/.vitepress/dist, then redeploy. For other frameworks, match whatever output path Zeabur's template for that framework expects, since there is no custom path setting.
When to use
You are seeing this: Issue zeabur/zeabur#41 (closed, 5 comments): Where does Zeabur put the build output for a static deploy? Use this skill when you run into "Where Zeabur deploys build output for a Vitepress project".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Sources
- https://github.com/zeabur/zeabur/issues/41
Evidence
In https://github.com/zeabur/zeabur/issues/41, the reporter asked: Issue zeabur/zeabur#41 (closed, 5 comments): Where does Zeabur put the build output for a static deploy? The reporter expected the default build command to deploy the dist folder at the project root and wanted to configure the output path. (Issue filed in Chinese; paraphrased.) The verified answer: At the time, Zeabur did not let users configure the build output path at all, per maintainer yuaanlin. For Vitepress projects specifically, the officially supported setup is: Zeabur runs the build or docs:build command, then serves the files from docs/.vitepress/dist as static output. So if your Vitepress deploy serves nothing, make sure your build script is named build or docs:build and your output lands in docs/.vitepress/dist, then redeploy. For other frameworks, match whatever output path Zeabur's template for that framework expects, since there is no custom path setting. Source thread: https://github.com/zeabur/zeabur/issues/41
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_Jjv3XYBaDSiYLxUhf20KuA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Where Zeabur deploys build output for a Vitepress project <span>— Vectle</span></a>