## 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.