Repository navigation
feat(notifications): add Apprise channel - #1908
Merged
Merged
Conversation
Send notifications through a self-hosted apprise-api server, which reaches 100+ services. Opt-in per notification type, with the server address and config key encrypted at rest. Refs discussion #1113
…ications # Conflicts: # backend/utils/notificationPreferences.js
This was referenced Oct 15, 2026
danathar-atomic-hive Bot
added a commit
to Danathar/tududi
that referenced
this pull request
Oct 15, 2026
chore: sync upstream chrisvel/tududi (chrisvel#1904, chrisvel#1908, chrisvel#1909)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds an Apprise channel, so tududi notifications reach any service an apprise-api server supports. Users save their server address and config key under Profile → Notifications, then opt in per notification type. The address and key are encrypted at rest, and private addresses follow the
CALDAV_ALLOW_PRIVATE_HOSTSrule used by calendar feeds.Type of Change
Related Issues
Refs discussion #1113
Testing
How did you test this?
Backend integration tests for config, encryption, SSRF checks and fan-out (14 tests), unit tests for preferences, a frontend card test, lint clean, and the migration run up and down on a scratch DB.
npm run pre-pushpassesChecklist
Additional Notes
The daily task summary is still Telegram only. Translation keys use English defaults for now.