Does anyone have already gained experience of integrating npm packages from a local GitLab server into the Node-RED Manage range? Does a script already exist to generate the catalog for Node-RED automatically?
Have a look at this blog post:
It covers how to add a custom node catalogue to supplement the default one hosted on flows.nodered.org. In the post I used a custom NPM registry but you should be able to use the full http:// url of the gitlab project as the
id field to install packages directly from the repo. (I've not actually tested this, but I think it should work)
Also it looks like you can use gitlab as a private npm repository (docs) so you could just use scoped node names as described in the post.
You might also be able to modify this script to build the catalogue file
thanks for the tutorial. First I implemented it exactly as you described it in the tutorial. That works very well :-). When integrating GitLab, however, I still failed because I couldn't get the data from package.json via the GitLab API. Maybe there is also a trick. But I still have to find out
Does anyone know whether GitLab can call up package.json from npm Packages?
the connection of the local NPM registry via a GitLab server worked. However, after each update of my own nodes, I have to restart node-red again and again. With nodes from the official catalog, I haven't noticed this message after updates. I always get the following message.
Node-RED must be restarted to enable upgraded modules
Do nodes have to be configured separately so that node-red does not have to be restarted after an update?
If you are installing a node for the first time, you don't have to restart.
But if you are upgrading an existing node, you must restart to complete the upgrade. That is true of all modules regardless of where they were installed from.
Thanks for the clarification. Although I never noticed it with nodes from the official catalog.
Is there a way to restart Node-RED by itself? I installed Node-RED as a service on Windows.