Deploy an Angular app in seconds
Angular builds the app into a nested folder, dist/<project-name>/browser, so build the project locally and upload exactly that folder. Tuqo serves the static files over HTTPS with a fallback to index.html for routing.
dist/<app>/browser · free SSL Build locally
ng build (or npm run build), and Angular puts the build into dist/<app>/browser.
Pack the browser build
tar -czf site.tar.gz -C dist/<app>/browser . 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
Published on a subdomain right away, free SSL, SPA routing works.
# build Angular locally
ng build
# pack the finished output (index.html must be at the root of the archive)
tar -czf site.tar.gz -C dist/<app>/browser .
# 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 Angular — frequently asked questions
Why not an automatic build? +
Angular puts the site into a nested folder, dist/<app>/browser, while Tuqo takes the whole of dist, which has no index.html at its root. So upload the ready browser build.
Does client-side routing work? +
Yes, there is a fallback to index.html, so Angular Router routes open directly.
Do I need Angular Universal (SSR)? +
No. For static hosting, use the regular browser build without SSR.