Operations
Operations
Running notify for real.
Program mode (native or Docker Compose) and the combined binary
What it is, how notify connects, auth, and versions
The fs and s3 adapters, with Garage
What to back up and what is purged
Health, readiness, metrics, tracing, analytics
The master key, rotation, the SSRF guard
Tags, artifacts, and upgrade notes
The shape of a deployment
- One notify process per database. State is a SQLite file, a single writer. Do not run two notify processes on one
NOTIFY_DB; scaling out is a datastore change, not a deployment change. - One dagnats sidecar that notify can reach over NATS and HTTP.
- A master key that never changes unless you re-key.
- Optionally a blob store and an MX/SMTP path for inbound mail.
- Something in front for TLS if you expose the API, such as a reverse proxy or a tunnel. notify itself serves plain HTTP.