Savannah Cloud

Self-hosting on Hetzner VPS

Deploy Savannah Cloud to a VPS with production-ready configuration and TLS.

Prerequisites

  • A VPS running Ubuntu 22.04 or later
  • SSH access to the host
  • A domain name (recommended for HTTPS and custom domains)
  • Cloudflare R2 credentials, DNS credentials, and app secrets for production

Savannah Cloud production deployment typically includes:

  • Go API server behind nginx or another reverse proxy
  • PostgreSQL database and Redis services
  • PowerDNS for delegated custom domain handling
  • Cloudflare R2 for build artifacts
  • Let’s Encrypt automation for TLS certificates
  • Prometheus metrics and health checks

Provision the server

ssh root@YOUR_SERVER_IP

Then install Docker and the Compose plugin, clone the repo, and configure the root .env file.

git clone https://github.com/Mbuthia71/distributed-task-queue.git
cd distributed-task-queue
cp .env.example .env

Set production secrets:

JWT_SECRET=... 
RESEND_API_KEY=... 
AT_API_KEY=... 
AT_USERNAME=... 
R2_ENDPOINT=... 
R2_ACCESS_KEY_ID=... 
R2_SECRET_ACCESS_KEY=... 
PDNS_API_KEY=... 

Start the platform

docker compose up -d --build app console

For the full service stack, run the compose stack in the project root.


Add TLS and public routing

Point your domain to the server and configure TLS. If using a reverse proxy, ensure:

  • port 80 is open for HTTP challenge traffic
  • port 443 is open for HTTPS
  • DNS records are in place for the application and custom domains

Use ACME automation with the ACME_EMAIL and DNS config to provision certificates automatically.


Monitoring and updates

Use health checks and Prometheus metrics to validate deployment health:

curl https://api.yourdomain.com/health
curl https://api.yourdomain.com/metrics

To update the deployment:

git pull
docker compose up -d --build app console

Security hardening

Production deployments should include:

  • least-privilege secret management
  • rate limiting at edge or app layer
  • WAF rules and ML-powered anomaly detection
  • isolated database and worker access
  • regional backup and log retention

The project includes support for self-hosted DNS, app routing, worker scaling, and centralized monitoring for real-world production use.

On this page