Gatus

​

Towbar manifest

id: gatus
name: Gatus
file: deploy/gatus/compose.yml
strategy: maintenance
services:
  gatus:
    port: 8080
    domains:
      - gatus.example.com
    ingress:
      type: proxy
environments:
  production:
    server: 192.0.2.10

​

Compose project

services:
  gatus:
    image: twinproduction/gatus@sha256:094eb186e55235db367e90e9d56140e5897b7044c41de23cde4cc18e6da1242e
    configs:
      - source: checks
        target: /config/config.yaml
configs:
  checks:
    file: ./config.yaml

endpoints:
  - name: Example site
    url: https://example.com
    interval: 1m
    conditions:
      - "[STATUS] == 200"

​

Configure

1. Prepare the example server, connect the repository, and map production to the branch containing these files. Replace the example server IP and domain.
2. Commit every file shown below under deploy/gatus/. The Towbar manifest points to the Compose file; it does not create it for you.
3. Sync the repository and inspect the resolved Compose project. Save the runtime values below if this example declares any.
4. Replace the example endpoint with a URL you control. Add alerting only after the basic check works; destination credentials belong in Towbar runtime secrets, not this file.
5. Deploy it manually and run the verification below before enabling auto-deploy.

​

Verify