Umami

​

Towbar manifests

id: umami-postgres
name: Umami PostgreSQL
type: postgres
container:
  network: application
  networkAlias: umami-postgres
  resources:
    cpus: 1
    memory: 1g
secrets:
  runtime:
    - POSTGRES_USER
    - POSTGRES_DB
    - POSTGRES_PASSWORD
environments:
  production:
    server: 192.0.2.10

id: umami
name: Umami
buildServer: null
deployment:
  type: image
  image: ghcr.io/umami-software/umami:3.4@sha256:6cd9d24a836fac5c226c3c90cb25141d4560b7270b7827f393ccf09bf3f83b18
container:
  port: 3000
  network: application
environments:
  production:
    server: 192.0.2.10
secrets:
  runtime:
    - DATABASE_URL
domains:
  primary: umami.example.com
tls:
  mode: direct

​

Configure

1. Prepare the example server, connect the repository, and map production to the branch containing these manifests. Replace the example server IP and domain. Commit the manifests, then sync the repository and inspect the resolved configuration.
2. Save the initialization values in the table below for the postgres Datastore under Datastore → Settings → Secrets. Deploy it first and wait for readiness. These values create the database and user only on an empty volume.
3. Set the Service’s declared runtime values under Service → Settings → Secrets using the table below. Replace descriptions and placeholders with actual values; do not commit passwords or keys.
4. Deploy the Service, then perform the checks below before enabling auto-deploy.

​

Datastore values

​

Runtime values

​

Verify