DevOps

How the Qubital system is built, tested, deployed, observed, and automated. This section covers operational infrastructure — not application features.

Sections

ci/

GitHub Actions CI pipeline for the Go backend. Covers the test strategy (unit tests, boot smoke test, race detection, linter), what runs on PRs vs manual triggers, and the branch model (trunk-based: main + short-lived feature branches).

deployment/

How each part of the system gets deployed:

Component	Platform	Trigger
Go backend (API server + worker)	Sevalla	Docker image pull from GHCR; manual prod release via workflow_dispatch
Cloudflare Workers (office-router, upload-worker)	Cloudflare Workers	wrangler deploy
Recording pipeline (livekit-listener + video-upload-job)	Google Cloud Run	build-publish.yaml workflow (workflow_dispatch)

observability/

How the system is observed in production:

• Logs — structured JSON logs via slog, shipped to Betterstack via samber/slog-betterstack
• Metrics — Prometheus metrics exposed at /metrics, remote-written to Grafana Mimir

automations/

Internal bots and automated workflows that run alongside the development process:

• ClickUp PR bot — creates, promotes, and closes ClickUp tasks based on GitHub PR lifecycle events
• Doc-writer agent — drafts documentation PRs on every code PR merge to main