Deploy Docusaurus in seconds
Docusaurus builds into build/. Tuqo builds the documentation site in a sandbox and publishes it over HTTPS. A great fit for technical docs and knowledge bases.
build/ · Node 20 · free SSL Upload the project
A .tar.gz or .zip archive with the Docusaurus sources (a lock file is recommended).
Build on Node 20
npm ci && npm run build, with the output taken from build/.
Published over HTTPS
The site is on name.tuqo.ru right away, free SSL, a custom domain from the Start plan.
# build locally and upload, or upload the sources and let Tuqo build them
npm ci && npm run build # output in build/
# pack the output (index.html must be at the root of the archive)
tar -czf site.tar.gz -C build .
# 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 Docusaurus — frequently asked questions
What is Docusaurus's output folder? +
build/, and Tuqo takes the output from there automatically.
Does it suit large documentation? +
Yes, Docusaurus static output is fast and search-friendly, great for docs.
Can I use my own domain? +
Yes, from the Start plan; on Free, as a paid add-on. The SSL certificate is issued automatically. Without a custom domain the site runs on its name.tuqo.ru subdomain.