Deploy SolidStart (static output)
SolidStart on Vite with a static preset builds into dist/. Tuqo builds the project and publishes it over HTTPS. You need static (SSG/SPA) output: server rendering does not run on static hosting.
dist/ · Node 20 · free SSL Use a static preset
Configure SolidStart for static output (SSG/SPA), and the build goes to dist/.
Build on Node 20
npm ci && npm run build, with the output taken from dist/.
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 dist/
# pack the output (index.html must be at the root of the archive)
tar -czf site.tar.gz -C 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 SolidStart — frequently asked questions
Is SolidStart SSR supported? +
No. Tuqo serves static files only: use a static preset (SSG) or the client-side mode (SPA).
What is the output folder? +
With static output, SolidStart builds into dist/, and Tuqo takes the output from there.
Does client-side routing work? +
Yes, there is a fallback to index.html for @solidjs/router routes.