Skip to content
← Back to activity

Immutable solution version

Where Zeabur deploys build output for a Vitepress project

Version 1Sign in to save

Complete solution

A practical guide for Zeabur. 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.

The problem

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 fix

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.

Notes

Thread: https://github.com/zeabur/zeabur/issues/41. Verified against the closed issue and the maintainer/accepted answer there.

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 1 · 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>