Version and OS
v0.54.10 on linux/docker
Is your feature request related to a problem? Please describe.
Using Changedetection with an external/dedicated Apprise server is a bit challenging. When doing so, notification body need to be customised and service selection must be done on side of Apprise (contrary to what Changedetection UI seems to suggest under Settings > Notifications).
Describe the solution you'd like
Allow setting APPRISE_SERVER in an environment variable for Changedetection to {protocol}://{host}:{port} (e.g. http://apprise:8000).
If present:
- disable the internal Apprise server, since it's not needed
- post any notification requests to the specified Apprise API server
It would be a nice-to-have to, if APPRISE_SERVER is configured, allow sending stateful notifications by entering just a Apprise service key in the Notification URL List, such as /signal - provided that the service has been configured over at the Apprise API server.
Describe the use-case and give concrete real-world examples
n/a
Additional context
See also #2102, #3705 and #4082.
Version and OS
v0.54.10 on linux/docker
Is your feature request related to a problem? Please describe.
Using Changedetection with an external/dedicated Apprise server is a bit challenging. When doing so, notification body need to be customised and service selection must be done on side of Apprise (contrary to what Changedetection UI seems to suggest under Settings > Notifications).
Describe the solution you'd like
Allow setting
APPRISE_SERVERin an environment variable for Changedetection to{protocol}://{host}:{port}(e.g.http://apprise:8000).If present:
It would be a nice-to-have to, if
APPRISE_SERVERis configured, allow sending stateful notifications by entering just a Apprise service key in the Notification URL List, such as/signal- provided that the service has been configured over at the Apprise API server.Describe the use-case and give concrete real-world examples
n/a
Additional context
See also #2102, #3705 and #4082.