Umami analytics

​

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. Register and prepare the example server or servers, connect the repository, and map production to the branch containing these files.
2. Save each Datastore credential value under Datastore → Settings → Secrets, deploy it first, and verify engine readiness before starting a dependent Service.
3. Save the Service’s declared keys in its selected environment, or enable and authorize the selected external-secret provider. Do not commit the values.
4. Set the Service’s DATABASE_URL to postgresql://<user>:<password>@umami-postgres:5432/<database>, using the user, name, and password you configured on the Datastore. A Docker network does not copy those values. Change Umami’s default administrator password after first login.
5. Sync the repository, inspect the resolved configuration, deploy manually, and perform the verification below before enabling automation.

​

Verify