tuqo
Deploy Jekyll

Deploy a Jekyll site in seconds

Jekyll is a Ruby generator, so Tuqo does not build it on the server. Build the site locally with jekyll build and upload the _site/ folder. Tuqo serves the static files over HTTPS with free SSL. A handy alternative to GitHub Pages.

Build locally → upload _site · free SSL
1

Build locally

bundle exec jekyll build, and Jekyll generates the static site in _site/.

2

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.

3

Upload to Tuqo

The site is on name.tuqo.ru right away, free SSL, a custom domain from the Start plan.

# build Jekyll locally (Ruby, not Node: Tuqo builds npm projects only)
bundle exec jekyll build

# 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 Jekyll — frequently asked questions

Why is Jekyll not built on the server? +

Tuqo builds only Node projects. Jekyll is written in Ruby, so build locally and upload the ready _site/ folder.

How is Tuqo different from GitHub Pages? +

Servers in Russia, so the site opens there without a VPN; version rollbacks on paid plans; deploys from an AI agent over MCP. Free SSL everywhere; a custom domain from the Start plan.

What exactly do I upload? +

The contents of _site/ (index.html and assets): drag the folder into the panel or pack it into a .tar.gz or .zip.

Deploy other stacks