[PR #493] [MERGED] Ntfy alerter: Add support for email notifications, notification titles and message priorities #2854

Closed
opened 2026-04-11 10:39:32 -05:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/moghtech/komodo/pull/493
Author: @FelixBreitweiser
Created: 5/7/2025
Status: Merged
Merged: 5/18/2025
Merged by: @mbecker20

Base: 1.17.6Head: main


📝 Commits (1)

  • 06b4d97 added support for ntfy email forwarding

📊 Changes

6 files changed (+51 additions, -15 deletions)

View changed files

📝 bin/core/src/alert/mod.rs (+2 -2)
📝 bin/core/src/alert/ntfy.rs (+13 -5)
📝 client/core/rs/src/entities/alerter.rs (+4 -0)
📝 client/core/ts/src/types.ts (+1 -0)
📝 frontend/public/client/types.d.ts (+1 -0)
📝 frontend/src/components/resources/alerter/config/endpoint.tsx (+30 -8)

📄 Description

Originally I only wanted a way to receive email notifications from komodo alerts, and found out that ntfy allows forwarding notifications via email by adding a "X-Email" header to a notification request. So I implemented that, and while I was at it, I also added support for customizing the notification title and message priority:

  • in the frontend when setting the alerter type to "ntfy", new configuration fields will pop up
  • the default notification title was change from "ntfy alert" to "Komodo Alert", and can be customized if desired
  • the main use-case for message priorities is for usage with the ntfy android app, which will notify the user more (or less) urgently (see the ntfy documentation)

For the future, maybe it would be nice to have email alert support directly as part of komodo, but that of course entails a bit more work than this:

  • email support could maybe be handled with the lettre crate?
  • smtp server configuration must be handled (as a resource, or just via core.config.toml?)
  • multiple email recepients could be supported (ntfy only supports one "X-Email" header, so for each email receipient a separate alerter must be configured, which should also be publishing to a different topic. Its all a bit inconvienient)

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/moghtech/komodo/pull/493 **Author:** [@FelixBreitweiser](https://github.com/FelixBreitweiser) **Created:** 5/7/2025 **Status:** ✅ Merged **Merged:** 5/18/2025 **Merged by:** [@mbecker20](https://github.com/mbecker20) **Base:** `1.17.6` ← **Head:** `main` --- ### 📝 Commits (1) - [`06b4d97`](https://github.com/moghtech/komodo/commit/06b4d97300ba2a4f96f1428aad5b4a8e2a478850) added support for ntfy email forwarding ### 📊 Changes **6 files changed** (+51 additions, -15 deletions) <details> <summary>View changed files</summary> 📝 `bin/core/src/alert/mod.rs` (+2 -2) 📝 `bin/core/src/alert/ntfy.rs` (+13 -5) 📝 `client/core/rs/src/entities/alerter.rs` (+4 -0) 📝 `client/core/ts/src/types.ts` (+1 -0) 📝 `frontend/public/client/types.d.ts` (+1 -0) 📝 `frontend/src/components/resources/alerter/config/endpoint.tsx` (+30 -8) </details> ### 📄 Description Originally I only wanted a way to receive email notifications from komodo alerts, and found out that ntfy allows forwarding notifications via email by adding a "X-Email" header to a notification request. So I implemented that, and while I was at it, I also added support for customizing the notification title and message priority: - in the frontend when setting the alerter type to "ntfy", new configuration fields will pop up - the default notification title was change from "ntfy alert" to "Komodo Alert", and can be customized if desired - the main use-case for message priorities is for usage with the ntfy android app, which will notify the user more (or less) urgently (see [the ntfy documentation](https://docs.ntfy.sh/publish/#message-priority)) For the future, maybe it would be nice to have email alert support directly as part of komodo, but that of course entails a bit more work than this: - email support could maybe be handled with the [lettre](https://crates.io/crates/lettre) crate? - smtp server configuration must be handled (as a resource, or just via `core.config.toml`?) - multiple email recepients could be supported (ntfy only supports one "X-Email" header, so for each email receipient a separate alerter must be configured, which should also be publishing to a different topic. Its all a bit inconvienient) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-11 10:39:32 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/komodo#2854