apprise-api

changes or architecture.

Devs) - a web service (you host) that can act as a sidecar. This solution allows you to keep your notification configuration in one place instead of across multiple servers (or within multiple programs). This one is for both Admins and Devs. A lot of systems have already adapted to it such as HomeAssistant, Apache Airflow, ChangeDetection, Uptime Kuma and many others (<https://github.com/caronc/apprise/wiki/showcase#integrations>) which shows the commonality. Mailrise is an incredibly talented program that converts Emails sent to it to trigger notifications via Apprise. What else does it do? 1. Emoji Support (:rocket:) built right into it! 2. File Attachment Support (to the end points that support it) 3. It supports inputs of `MARKDOWN`, `HTML`, and `TEXT` and can easily convert between these depending on the endpoint. For example: HTML provided input would be converted to TEXT before passing it along as a text message. However the same HTML content provided would not be converted if the endpoint accepted it as such (such as Telegram, or Email). 4. It supports breaking large messages into smaller ones to fit the upstream service. Hence a text message (160 characters) or a Tweet (280 characters) would be constructed for you if the notification you sent was larger. 5. It supports configuration files allowing you to securely hide your credentials and map them to simple tags (or identifiers) like `family`, `devops`, `marketing`, etc. There is no limit to the number of tag assignments. It supports a simple TEXT based configuration, as well as a more advanced and configurable YAML based one. 6. Configuration can be hosted via the web (even self-hosted), or just regular (protected) configuration files. 7. It Supports "tagging" of the Notification Endpoints you wish to notify. Tagging allows you to mask your credentials and upstream services into single word assigned descriptions of them. Tags can even be grouped together and signaled via their group name instead. 8. Dynamic Module Loading: They load on demand only. Writing a new supported notification is as simple as adding a new file; see here: https://github.com/caronc/apprise/tree/master/apprise/plugin... 9. Developer CLI tool (it's like `/usr/bin/mail` on steroids) It's worth re-mentioning that it has a fully compatible API interface found here: <https://github.com/caronc/apprise-api> or on Dockerhub (<https://hub.docker.com/r/caronc/apprise>) which has all of the same bells and whistles as defined above. This acts as a great side-car solution! Program Details - Entirely a self-hosted solution. - Written in Python - 99.27% Test Coverage (oof... I'll get it back to 100% soon) - BSD-2 License - Over 450K downloads a month on PyPi - Over 2.8 million downloads from Docker Hub I would love to hear any feedback any of you have!

figuration`. You just need to define the schemas you use, and then you can already use Apprise. Check out the list of the services available today here: https://github.com/caronc/apprise#supported-notifications Apprise is 100% open source (MIT Licensed). It has an acompanied API I built for those who want to centralize their configuration (found here: https://github.com/caronc/apprise-api). Some reasons you may also all find it useful: - It works perfectly with legacy servers (supporting even Python 2.7). So this fits system admins using older systems such as CentOS 6+ - It has a complete API that developers, devops, and administrators alike can leverage allowing them to control the notifications in their environments. - It supports configuration files allowing you to securely hide your credentials and map them to simple tags like `family`, `devops`, `marketing`, etc. There is no limit to the number of tag assignments. It supports a simple TEXT (https://github.com/caronc/apprise/wiki/config_text) based configuration, as well as a more advanced and configurable YAML (https://github.com/caronc/apprise/wiki/config_yaml) based one. - It sends all notifications asynchronously optimizing setups where there are many end-points to deliver to. - It supports inputs are of MARKDOWN, HTML, and TEXT and can easily convert between these depending on the endpoint. For example: HTML provided input would be converted to TEXT before passing it along as a text message. However the same HTML content provided would not be converted if the endpoint accepted it as such (such as Telegram, or Email). - It supports breaking large messages into smaller ones to fit the upstream service. Hence a text message (160 characters) or a Tweet (280 characters) would be constructed for you if the notification you sent was larger. - It supports file attachments too. So feel free to pass along an image, PDF, etc if the destination supports it. - It can easily allow you to write your own custom notifications and/or simply leverage Apprise as routing service to perform admin tasks for you. See here for more details: https://github.com/caronc/apprise/wiki/decorator_notify - It has 100% code based test coverage. :) I hope to continue to add more services (and break 100+ supported services someday). I also hope some of you find it useful for your own project solution!