Deploy Storybook in seconds
Storybook builds into a non-standard folder, storybook-static/, so build it locally with build-storybook and upload the ready folder. Tuqo serves the static files over HTTPS with free SSL.
storybook-static · free SSL Build locally
npm run build-storybook, and Storybook generates the static site in storybook-static/.
Pack the output
tar -czf site.tar.gz -C storybook-static . 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 Storybook locally
npm run build-storybook
# pack the finished output (index.html must be at the root of the archive)
tar -czf site.tar.gz -C storybook-static .
# 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 Storybook — frequently asked questions
Why not an automatic build? +
Tuqo recognizes the storybook-static folder, but it is created by a separate command, build-storybook, not by npm run build (which builds the app itself). So build locally.
What exactly do I upload? +
The contents of storybook-static/ (index.html and assets): drag the folder into the panel or pack it into a .tar.gz or .zip.
Do I need a server? +
No. A built Storybook is plain static files; no server code runs on the hosting.