Files
terdut-server/docs/README.md
T
Niklas Ye b114251f45 Add notification channels and a provider abstraction
Users get a notification_channels table (replacing users.ntfy_topic); pages fan
out to every enabled channel through a notify.Provider registry, with ntfy as
the first provider. Fallbacks are typed {type, address}. Schema edited in place:
existing databases must be recreated.

Claude-Session: https://claude.ai/code/session_016mBLURvJoMuUEr9cB2RpUN
2026-10-12 21:00:40 +02:00

22 lines
1.2 KiB
Markdown

# Terminal Duty documentation
The [README](../README.md) is the short tour. These pages hold the detail.
**Running it**
- [Deployment](./deployment.md): Docker, the Helm chart, the database, backups, and the operator.
- [Configuration](./configuration.md): environment variables and settings.
- [Single sign-on](./single-sign-on.md): OIDC, group mapping, the terminal device flow.
**Using it**
- [The web UI](./web-ui.md): sessions, the Team and Admin tabs.
- [Alertmanager configuration](./alertmanager.md): routes, integration keys and webhooks.
- [Alerts and incidents](./incidents.md): correlation, lifecycle, on-call assignment, stale-alert expiry.
- [Notifications](./notifications.md): channels and providers, ntfy pages, and acknowledging from them.
- [Escalation](./escalation.md): ladders, repeats and the fallback.
- [Dead man's switches](./dead-mans-switch.md): noticing that alerts stopped arriving.
**Integrating and contributing**
- [API reference](./api.md): every endpoint, authentication and error shape.
- [Service accounts](../SERVICE-ACCOUNTS.md): non-human credentials for automation.
- [Development and releasing](./development.md): tests, the CI gate, the release pipeline.