Deploy VitePress in seconds
VitePress builds the site into .vitepress/dist inside the docs folder, not the usual dist at the root, so build locally and upload the ready folder. Tuqo serves the documentation over HTTPS.
docs/.vitepress/dist · free SSL Build locally
npm run docs:build, and VitePress generates the static site in docs/.vitepress/dist.
Pack the output
tar -czf site.tar.gz -C docs/.vitepress/dist . puts index.html at the root of the archive. A .zip works too, and in the panel you can simply drag the folder in.
Upload to Tuqo
The site is on name.tuqo.ru right away, free SSL, a custom domain from the Start plan.
# build VitePress locally
npm run docs:build
# pack the finished output (index.html must be at the root of the archive)
tar -czf site.tar.gz -C docs/.vitepress/dist .
# deploy over REST (or from the panel, or from an AI agent over MCP)
SITE=<site_id> # from the panel or list_sites
curl -X POST https://api.tuqo.ru/api/v1/sites/$SITE/deploys \
-H "Authorization: Bearer tqk_xxx_yyy" \
-H "Content-Type: application/gzip" \
--data-binary @site.tar.gz
The command line is not the only way: in the panel you can simply drag the site folder
in, and instead of .tar.gz a
.zip works too — Tuqo detects the archive
format by itself.
Deploying VitePress — frequently asked questions
Why not an automatic build? +
Tuqo looks for .vitepress/dist at the project root, while a typical VitePress project keeps it inside docs/. Keep the docs at the root and we build it for you; otherwise upload the ready folder.
Where is the build? +
Usually docs/.vitepress/dist; the path depends on where the documentation sources live.
Does it suit large documentation? +
Yes, VitePress is fast and search-friendly, a good fit for technical docs.