GoRunner docs
Search or askSearch⌘K

Self-host

Run GoRunner on your own server. On GoRunner Cloud, GoRunner runs all of this for you.

Start here

Install with DockerOne Linux server, automatic HTTPS · 15 min

Docker or Kubernetes

How it fits together

People’s browsers reach caddy on ports 80 and 443. Caddy passes them to the API gate on port 3001, which holds two copies of the API. The API and the worker both use Postgres, Redis and the file store. Browsersand other apps caddyHTTPS · 80, 443 api-gate · port 3001 apiapi-twin workerruns the workflows postgresworkflows, runs, people rediswake-ups and sessions seaweedfsfiles for step data The same picture, top to bottom: browsers, caddy, the API gate with api and api-twin, the worker, then Postgres, Redis and the file store. Browsersand other apps caddyHTTPS · 80, 443 api-gate · port 3001 apiapi-twin workerruns the workflows postgresworkflows, runs, people rediswake-ups and sessions seaweedfsfiles for step data
GoRunner’s own containers all run one image. migrate runs once on each start and update, then stops. Each store can be your own instead.

Common tasks

Look something up: Settings (.env) · Helm values · The preflight check · Containers, ports and volumes · Health checks · Metrics · Traces · Logs.