NTFY: NodeBB

julian

Unfortunately not at this time, although the desire to self-host the ntfy instance is definitely something that (I imagine) is top-of-mind for ntfy's creator.

It's also a given that as ntfy becomes more popular, that pressure will increase to add limits to the free plans, so it would be in our best interest to be able to handle our own ntfy backend.

I don't know how that will look yet... whether it's something NodeBB offers for all NodeBB instances... but at the very least we would want to update the plugin to be able to support sending notifications to different ntfy servers.

phenomlab

@julian said in NTFY: NodeBB:

I don't know how that will look yet... whether it's something NodeBB offers for all NodeBB instances... but at the very least we would want to update the plugin to be able to support sending notifications to different ntfy servers.

Yes, see my post above. It's possible to self-host, but the plugin would need to be adjusted to support that.

julian

One possible case scenario, of course, is if the ntfy binary is literally shipped with the plugin, then we can actually have each NodeBB self-host their own ntfy server.

Realstically, however, I do not know how feasible that is.

Edit: ... not to mention, NodeBB doesn't have plans to be an OS...

Edit 2: ... or does it...

phenomlab

@julian ok, I have a self-hosted version working in principle, so all I need now is the modified plugin, which I'm happy to test

phenomlab

@julian any chance of a version of this plugin that enables you to choose your own local installation instead of ntfy.sh ?

julian

@phenomlab Yes, I am just tied up with other projects at the moment, but thank you for the reminder

julian

If you want to play around with it today, go into node_modules/nodebb-plugin-ntfy/lib/ntfy.js.

All calls to ntfy.sh go through ntfy.send, and you can change the value in line 61 to send it to your own service.

The change I need to make is to introduce ACP controls, etc... but you can edit that value to get unblocked today.

phenomlab

@julian perfect. Thanks. Will try this out and let you know.

phenomlab

@julian think I found a bug. The topic ID does not seem to work if it contains a period (in my case, sudonix.dev-phenomlab...) in the sense that you cannot subscribe to this ID in the ntfy client (it works if you remove the period, but of course, nothing is sent).

julian

That's odd... the topic ID when regenerated should slugify the hostname, so it should end up being sudonix-dev-phenomlab..., no periods.

For example, on here, my topic ID is community-nodebb-org-julian-hahadidyouthinkidpostmyrealid, the dots are replaced with dashes.

phenomlab

Ok, let me try that.

phenomlab

Interesting. If I regenerate, the slugify works correctly, so sudonix.dev-phenomlab becomes sudonix-phenomlab

phenomlab

And... works perfectly !!

phenomlab

@julian any update around the self hosted ntfy ?
Thanks

julian

@phenomlab not yet, but the edited file works fine for you for now, right?

phenomlab

@julian yes, but of course, any released update would override this change.

julian

Indeed it would I'll see if I can find time to work on it this week

phenomlab

@julian perfect. Thanks

phenomlab

Hey @julian,

Not sure the NTFY plugin works properly for self-hosting. I have configured my instance on https://notify.sudonix.org, and am able to send messages to it via cURL, but the settings in NodeBB don't do anything when you test it - no message is ever recieved.

EDIT - it DOES work, but if you click the subscribe link, it points to ntfy.sh instead of your chosen server. If I manually subscribe then test the notification, it works correctly.

julian

@phenomlab thanks, will get that bug fixed up.