Add Telegram and Pushover as notification channels
Both send to one fixed address each (api.telegram.org, api.pushover.net), take part in routing rules and the channel count, have a Send test that shows the service's own refusal, and keep their tokens and keys encrypted and out of errors and the audit log. A Telegram message carries one button, and a Pushover message one link, to the page where an alert can be acknowledged, silenced or snoozed. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
9f366c37de
commit
31f4debb9a
22 files changed
+670
-37
No files matched your search
+2
-2
@@ -16,7 +16,7 @@ APP_BASE_URL=https://homelab.example.lan
|
||||
SESSION_SECRET=change-me-to-a-random-64-char-hex-string
|
||||
|
||||
# 32-byte (64 hex char) key used to encrypt stored integration API tokens, and the
|
||||
# notification channels' credentials (Gotify/ntfy tokens, SMTP password, webhook
|
||||
# notification channels' credentials (Gotify/ntfy/Telegram tokens, Pushover keys, SMTP password, webhook
|
||||
# secret), at rest (AES-256-GCM). Generate the same way as SESSION_SECRET.
|
||||
# Losing/changing this key makes those stored credentials unreadable.
|
||||
CREDENTIALS_ENCRYPTION_KEY=change-me-to-a-random-64-char-hex-string
|
||||
@@ -38,5 +38,5 @@ AUTHENTIK_ISSUER_URL=https://authentik.example.lan/application/o/homelab-manager
|
||||
AUTHENTIK_CLIENT_ID=
|
||||
AUTHENTIK_CLIENT_SECRET=
|
||||
|
||||
# Notification channels (Gotify, ntfy, SMTP, webhook) are configured in-app
|
||||
# Notification channels (Gotify, ntfy, Telegram, Pushover, SMTP, webhook) are configured in-app
|
||||
# under Settings, not here.
|
||||
Reference in new issue
Block a user