@AOKP OK, I've had a first crack at a nodebb-plugin-onesignal notifier. You can give it a try here.

https://github.com/CCob/nodebb-plugin-onesignal

Ignore the README, it was forked and modified from the pushbullet plugin and I haven't got around to updating the README and publishing on npm yet.

You need to populate your OneSignal app_id and API key within the admin section. You can get this from the OneSignal website under your applications Keys & Id section

I haven't done the Android integration yet, but you can get your player_ids from the OneSignal site here

https://onesignal.com/apps/your_app_id/players

I have exposed a REST API for adding player id's at /api/me/onesignal/devices. An authenticated POST with either a valid cookie or bearer token from the nodebb-plugin-write-api will work with the following JSON body

{
	"player_id" : "player-id-here"
}

Once this has been completed, notifications should work which you can test by going to the OneSignal settings within your profile.

Appreciate any feedback

I've been looking at this today for my own use. I have figured out the problem on why it doesn't work anymore. The delay loading of images feature has broken this plugin. Essentially the a links no longer exist to inject the fancybox API onto during the action:ajaxify.end notification. Unfortunately I'm new to nodebb plugins so I'm looking for an appropriate event I can listen on after the links get injected during the Post.wrapImagesInLinks. Does anyone have any suggestions?

Thanks

Take a look here.

https://community.nodebb.org/topic/10267/nodebb-webview-app-v3/8

First attempt. Not ready for production use yet but can be tested if you are a developer or know what you are doing with REST calls.

@Braulio-Cesar-Holtz-Ribeiro The android app integration is not complete yet, so the automatic registration of the player_id wont work with the version @AOKP has compiled. Hence the need to manually populate player_id's using the REST endpoint exposed by nodebb-plugin-onesignal

@MBFTOM There is nothing stopping the onesignal plugin to work with iOS but there is no iOS WebView app to make use of it yet.

@kenygamer It's a native android application to allow viewing of a NodeBB compatible forum.

@meetdilip Yes, although you need to configure nodebb-plugin-onesignal on your NodeBB install too.

@aokp Are you planning on publishing where you got to with v4?

Which news forum software did you decide on?

@aokp Looking forward to it

@MBFTOM There is nothing stopping the onesignal plugin to work with iOS but there is no iOS WebView app to make use of it yet.

@WwoeSsi Integration is comple and works bar some documentation. You will need the nodebb-onesignal-plugin and also the Android application that @AOKP wrote with my additional onesignal commits. You also need to remember to register your onw application ids and change them in your WebView app.

@meetdilip Yes, although you need to configure nodebb-plugin-onesignal on your NodeBB install too.

@kenygamer It's a native android application to allow viewing of a NodeBB compatible forum.

@Braulio-Cesar-Holtz-Ribeiro The android app integration is not complete yet, so the automatic registration of the player_id wont work with the version @AOKP has compiled. Hence the need to manually populate player_id's using the REST endpoint exposed by nodebb-plugin-onesignal

@Braulio-Cesar-Holtz-Ribeiro Did you use the REST api exposed by the plugin to add the playerid from one signal as explained in my original post?

@Jenkler It's not on play store. It's designed to be taken and modified to suit your own forum URL's. So the demo version only works with the NodeBB community version.

@PitaJ said in Best way to get base URL from client side JS:

config.relative_path

So would I simply take location.origin + config.relative_path as the root to the NodeBB install?