CI/CD for a static site without GitHub Actions
To publish a static site on every commit, people often reach for GitHub Actions: they
write a .yml pipeline, set up build steps and secrets, sometimes run their own runner. For
a regular static site that is overkill. Tuqo gives you the same result, push → site in
production, with no YAML and no runners.
The difference
| GitHub Actions + hosting | Tuqo Git CD | |
|---|---|---|
| Config | a .yml pipeline written by hand | none, you link the repo in the panel |
| Build | your own steps and runners | automatic: Node 20, npm ci && npm run build |
| Deploy secrets | set up by hand | not needed |
| Webhook | — | created automatically |
| Rollback | by hand | one click (paid plans keep several versions) |
How to set it up
- Open the site in the Tuqo panel → the Git CD tab.
- Connect a Git service: GitHub or GitFlic with your account; GitVerse, GitLab or Gitea with an access token (for self-hosted GitLab or Gitea, enter your instance URL).
- Pick the repository and the production branch → Link. The webhook is created for you.
From then on it is business as usual: git push to the production branch, and the new
version is published automatically.
What about the build
Tuqo detects the project type on its own:
package.jsonpresent → a build on Node 20, output taken fromdist/,build/orout/(Vite, React, Vue, Astro, SvelteKit static, Next.js export and more);- no
package.json→ published as is (index.htmlmust be at the root).
The build runs in an isolated sandbox with time and memory limits. The hosting is static only: server code (SSR, PHP, a Node server) does not run.
When you still need GitHub Actions
If you need custom steps (tests, linters, generating content from external APIs at build time, a non-standard runtime), Actions is more flexible. You can keep that pipeline and publish its output to Tuqo with one CLI command; see deploy from GitHub Actions and GitLab CI. But for “build the frontend and publish the static files”, Git CD does the job without a pipeline.