[Nextcloud] Verify thoroughness of implementation over Apprise #671
Labels
documentation
help wanted
quality
All things QA, software tests, and maintenance
service plugin
All about service plugins
Dear @sevmonster,
similar to what we have been doing at GH-632, and after learning at 1 that you are also using Nextcloud, I think we could have a look at the corresponding
mqttwarn -> Nextcloud
implementation, which is currently also using Apprise 23. I don't expect any big problems, but who knows, we all know the devil is in the details, right?The general idea behind that, is, that I would like to bring more full end-to-end tutorials to the documentation, preferably the ones which are exclusively using open source components, in a spirit like the recently added Frigate-to-ntfy, OwnTracks-to-ntfy, and the URL-to-mediaplayer examples. 456
Would you be up for assisting in this task if you can find the time? Our work-sharing would be that I am humbly asking you to evaluate it, and, if it works out of the box, including attachments, you would send me working configuration/code snippets, and I would put them into a corresponding documentation file. If it does not work, or would need improvements, we will check what would be needed to make it work properly, like we did together well with the Frigate-to-ntfy example.
Maybe this idea can spark your interest?
With kind regards,
Andreas.
Footnotes
https://github.com/zulip/zulip/issues/25458 ↩
https://github.com/caronc/apprise/wiki/Notify_nextcloud ↩
https://github.com/caronc/apprise/wiki/Notify_nextcloudtalk ↩
https://mqttwarn.readthedocs.io/en/latest/examples/frigate/README.html ↩
https://mqttwarn.readthedocs.io/en/latest/examples/owntracks-ntfy/readme.html ↩
https://mqttwarn.readthedocs.io/en/latest/examples/mediaplayer/readme.html ↩
The text was updated successfully, but these errors were encountered: