Notifcation Improvements

[peaklabs-dev]

More notification options:

• Amazon SES for email
• slack
• whatsapp
• signal
• matrix
• teams
• push notifications for phone and pcs -> maybe browser based push notifications

-> and a webhook option ao we can use external services like zapier:

• webhook

Other notification improvements:

• make it possible to add multiple notification providers of the same type (2 different smtp servers)
• backup SMTP server selection if 1 one fails
• add more notifications for more different things, backup, healthecks, proxy check, deployments, statistics (ram usage)...
• add more granular notification control for example select when to recive backup notifications -> only if it fails and only for a few production databases or add error notification -> when deployments fail and not always
  ....
• Send a notification always when an admin logs into coolify
• Update notifications for coolify panel updates
• Update notifications for docker images: [Feature]: Add update monitoring (and possibility for auto upgrades) of services and all containers #2500

[yohannlog]

Hi! I did a PR for the first request: #2601

[peaklabs-dev]

Hi! I did a PR for the first request: #2594

Thank you so much.

[RayBB]

@yohannlog @ayntk-ai how would you feel about integrating with apprise so that just about any platform could be used to send notifications?
https://github.com/caronc/apprise
changedetection.io uses this and it works quite nicely!

[peaklabs-dev]

@yohannlog @ayntk-ai how would you feel about integrating with apprise so that just about any platform could be used to send notifications?
https://github.com/caronc/apprise
changedetection.io uses this and it works quite nicely!

Looks nice, but I and also the maintainer I believe do not like external dependecies that are not absolutely necessary. So native integrations would be better. But overall I would have nothing against this, maybe in addition to native integrations for some more neach providers.

[peaklabs-dev]

I think native notifications should be (as they are the most common):

• email
• Amazon SES for email
• slack -> pull request open
• discord
• telegram
• whatsapp
• signal
• matrix
• teams
• push notifications for phone and pcs -> maybe browser based push notifications

-> and a webhook option ao we can use external services like zapier:

• webhook

[yohannlog]

@yohannlog @ayntk-ai how would you feel about integrating with apprise so that just about any platform could be used to send notifications? https://github.com/caronc/apprise changedetection.io uses this and it works quite nicely!

Even if I like this solution, the problem is that you have to write the pages and code to support all the options for this package, so I don't know if it would be a time saver.

Besides, I don't know if this would be of much interest to the owner of this repo. Mainly for safety reasons.<

Edit: I will re-create the PR because I push it on the main (in my repo) and not a new branch

[RayBB]

For context, this is how change detection uses apprise.
As far as I know, it is only used on this page and the page for manual overrides.

[yohannlog]

For context, this is how change detection uses apprise. As far as I know, it is only used on this page and the page for manual overrides.

I will take a look. But the notification body is a great idea.

[madebyjulz]

It would be also great to just send notifications when anything doesnt works and not always.

[nullishamy]

@peaklabs-dev #3147 would appreciate some thoughts on this one - as it has a few upvotes now and would be greatly helpful for a deployment of coolify I plan on doing

[p3drosola]

I've been using the Discord notification option as a generic webhook notification.

Instead of setting a discord url, I send the payload to n8n, and from there to slack or wherever. Maybe it would be enough to make the Discord notification a bit more generic, add support for a basic auth header or something and call it a day.

[ClusterDuckster]

I've taking a liking to ntfy.sh for all my notifications. It has it's own service template in coolify alrerady, so it would feel natural to me to implement it as a notification target.

A webhook notification with an authentication option and ability to define a body template would be enough to enable basically all features of ntfy.sh.
A native integration example could be found at uptime-kuma. That would also be nice for me, but I don't know how many people here use ntfy.sh.

I've been using the Discord notification option as a generic webhook notification.

I will try that with ntfy.sh as well, thanks for the tip!

[50l3r]

Maybe it would be great to be able to configure notifications per project.

I have a discord server which I divide into channels according to each project. It would be great to be able to receive alerts about the deploys in each channel respectively 😁😁

[OliverGeneser]

@peaklabs-dev You mentioned wanting to keep external dependencies low. For the signal notifications, would the Signal REST API be acceptable, or would you prefer direct use of signal-cli?

[peaklabs-dev]

You can check how the current providers are implemented to get a good idea.