Deploy a Nuxt site (static generation)
Nuxt produces static output with a separate command, nuxi generate; a plain npm run build creates an SSR app, which cannot run on static hosting. So build the project locally and upload the ready .output/public folder. Tuqo publishes the static site over HTTPS.
.output/public · free SSL Generate the site
Locally: npx nuxi generate, and Nuxt writes the static site to .output/public.
Pack the output
tar -czf site.tar.gz -C .output/public . 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
From the panel, the CLI or an AI agent: the site is on name.tuqo.ru right away, free SSL.
# build Nuxt locally
npx nuxi generate
# pack the finished output (index.html must be at the root of the archive)
tar -czf site.tar.gz -C .output/public .
# 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 Nuxt — frequently asked questions
Why not an automatic build? +
Tuqo runs npm run build, and for Nuxt that is an SSR build, not static output. Tuqo does recognize the .output/public folder, but only nuxi generate fills it, so run that yourself.
Is Nuxt SSR supported? +
No, only static generation (SSG). Server rendering and API routes do not run.
What exactly do I upload? +
The contents of .output/public (index.html and assets): drag the folder into the panel or pack it into a .tar.gz or .zip.