@pitaj please have look at
Issue on reaching out to new routes established using the WriteAPI
where my mate described the approach and the issue in more detail.
The proper way to deploy a custom plugin
-
I needed two customised plugins for our forum (one scaled back FB SSO and one for bulk user creation). Initially I had huge problems making the plugins actually show up. I ended up adding symbolic links to each from node_modules.
That way they showed up as "installed" and could be activated.
However, is this really "the right way" of doing it? The docs say use "npm install" (which installed the dependencies but not much more). What's the proper way of deploying a plugin that's not made for public use?
-
npm install supports local folders
source -
@phit can you explain how you mean?
-
run this in your nodebb directory
npm install /path/of/your/pluginfolder -
Symbolic links are absolutely fine. It's the way I do all my plugins. NPM can even manage links for you using
npm link
