Deploy Eleventy (11ty) in seconds
Eleventy builds the site into _site/ by default. Tuqo recognizes that folder but only runs npm run build. If package.json has that script, upload the sources and we build it; if not, build locally and upload the ready folder.
_site · free SSL Build locally
npx @11ty/eleventy (or npm run build), and 11ty generates the static site in _site/.
Pack the output
tar -czf site.tar.gz -C _site . 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 Eleventy (11ty) locally
npx @11ty/eleventy
# pack the finished output (index.html must be at the root of the archive)
tar -czf site.tar.gz -C _site .
# 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 Eleventy (11ty) — frequently asked questions
Can I skip the local build? +
Yes, if package.json has a build script (usually "eleventy"): Tuqo runs npm run build and takes the output from _site/, a folder it recognizes.
What do I upload by default? +
The contents of _site/ (index.html and assets): drag the folder into the panel or pack it into a .tar.gz or .zip.
Is there HTTPS? +
Yes, free SSL is switched on automatically.