CI Agent
A single-binary CI/CD agent for offline / air-gapped Ubuntu servers that build and deploy Docker Compose stacks behind a manually-managed host nginx.
What it does
- Receives a webhook with a git URL (or a ZIP file URL), fetches the sources, and runs a deployment — or deploys a prebuilt image / pasted compose with no source at all.
- Builds every
build:service in the project’sdocker-compose.yml, tagging images per run so old versions stay redeployable. - Optionally runs your tests (
ci-testservice) before deploying. - Deploys with
docker compose up -d, health-gates the result, and automatically rolls back to the last good version on failure. - Manages each project’s nginx server block and TLS — multiple domains with a primary domain that the others 301-redirect to, per-domain HTTPS, and certificates from an internal CA, self-signed, uploaded, or Let’s Encrypt.
- Serves this admin UI: running jobs, deployment history, live run and container logs, redeploy, Docker cleanup tools, server resource gauges, and manual runs from a git URL or an uploaded ZIP.
Design at a glance
| Property | Choice |
|---|---|
| Footprint | one ~6 MB fully-static binary, embedded SQLite, no external services |
| Pipeline | convention over configuration: the compose file is the pipeline |
| Concurrency | serial per project, capped across projects |
| Offline | works with no internet: each deploy tries to pull newer images and quietly uses the local ones when it can’t; no CDN, no telemetry |
| Proxy | plain host nginx; the UI generates each project’s server block and can apply it in one click (or shows the commands to run yourself) |
| Distribution | signed apt repository (apt-get upgrade keeps it current) or a .deb/binary you transfer by hand; built automatically from every commit |
| Updates | apt, the Maintenance page’s built-in self-update, or scp — your choice |
Where to go next
New here? Start with Installation, then take the UI tour.
- Installation — get it running in five minutes.
- Admin UI guide — a tour of every page in the panel.
- Project conventions — what a deployable repo must look like.
- Webhooks — trigger deployments from anywhere, and get each run’s status sent back to your own URL.
- API & AI agents — API keys for scripts and AI agents.
- Domains & TLS — multiple domains, nginx, certificates.
- Reverse tunnel — serve a NAT’d box through a public one.
- Configuration — every config.toml key.
- Operations — queueing, rollback, retention, backups.
- Security — auth model, two-factor login, exposure guidance.
- Troubleshooting & FAQ — common problems and quick answers.