|
Some other apps, fully integrate apprise into themselves, meaning there is no need for an external apprise service. Meaning you then supply an apprise style destination URL. Examples as far as I remember are uptimekuma and bazarr. Other apps do not integrate apprise but offer the option of using an external apprise service giving the option of configuring the message/body and only ask for an apprise tag as destination. This second case is what I was expecting when I saw that geopulse now supports apprise notifications. Is there a specific reason for this implementation which escapes me at the moment? |
Replies: 2 comments
|
Hello, You're not missing anything. Apprise was added a simple transport layer that takes care about notification delivery. From my point of view it as the easiest and fastest way to deliver notifications for users who didn't have Apprise installed and configured (like myself). Config Key and Tag is a reasonable alternative and I can add them as well. So the user can specify either Apprise URLs (according to their format) or Config Key + TAG and let Apprise take care about the notification. Will do this in one of the next releases. Thanks. |
|
Implemented in 1.30.0 - https://github.com/tess1o/geopulse/releases/tag/v1.30.0 |
Hello,
You're not missing anything. Apprise was added a simple transport layer that takes care about notification delivery. From my point of view it as the easiest and fastest way to deliver notifications for users who didn't have Apprise installed and configured (like myself). Config Key and Tag is a reasonable alternative and I can add them as well. So the user can specify either Apprise URLs (according to their format) or Config Key + TAG and let Apprise take care about the notification.
Will do this in one of the next releases.
Thanks.