ntfy

​

Towbar manifest

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

​

Compose project

services:
  ntfy:
    image: binwiederhier/ntfy:v2.15.0@sha256:aa10e84da624f65be107f9317dbf6e212fa812e0ebf62e74d032d0762eccc930
    command:
      - serve
    configs:
      - source: server
        target: /etc/ntfy/server.yml
    volumes:
      - data:/var/cache/ntfy
configs:
  server:
    file: ./server.yml
volumes:
  data: {}

base-url: https://ntfy.example.com
cache-file: /var/cache/ntfy/cache.db
auth-file: /var/cache/ntfy/user.db
auth-default-access: deny-all

​

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/ntfy/. 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. Create an administrator with ntfy’s user add --role=admin command in the running container before publishing private topics. deny-all blocks anonymous reads and writes by default.
5. Back up the data volume if cached notifications or account records must survive server loss.
6. Deploy it manually and run the verification below before enabling auto-deploy.

​

Verify