-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for self-hosted ntfy instances #8
Comments
Sure, that seems doable, let me have a look and I'll tag you on a PR |
Thank you very much. I've validated the improvement on behalf of GH-10. It works well. 💯 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Dear Victor,
thanks a stack for conceiving and maintaining this excellent package.
Over at mqttwarn, we used to use Apprise to submit notifications to ntfy, which worked great. However, because we wanted to have better control within mqttwarn, we are adding a dedicated mqttwarn ntfy adapter now, see mqttwarn ntfy adapter documentation.
We had a look at your
ntfy-wrapper
package, but have not been able to use it right away, because it currently does not support self-hosted ntfy instances.ntfy-wrapper/ntfy_wrapper/notifier.py
Lines 406 to 410 in 8d5e28c
We think it would be so sweet if
ntfy-wrapper
could gain a feature to be able to define the ntfy HTTP API baseurl in some elegant way, in order to make using the library on self-hosted instances a first-citizen use case.With kind regards,
Andreas.
/cc @binwiederhier
References
ntfy
mqtt-tools/mqttwarn#638The text was updated successfully, but these errors were encountered: