An alternative installer for Node-RED. Avoids global installs, no admin rights required for new Node-RED instances.
This solution is particularly suited for development environments and anywhere that you don't want to install global NodeJS scripts. Also when you need to have different versions of Node-RED running in parallel.
- Make sure that you have Node.JS correctly installed. Check that you can run it manually from the command line with
node --version && npm --version.
- Make sure that Node.js is at least at version 8.16.0 (LTS) or above.
- For ease of use, install this package globally with
npm install -g alternate-node-red-installer. You may need to use a command line with elevated rights (
Now, from any command line, you should be able to run the following:
alternate-node-red-installer -f <root folder name>
Where ` is a relative or absolute folder path that you want to be the root of your new Node-RED installation.
Instead of the long-winded executable name, you can also use
Example (for Mac, Linux or Windows PowerShell):
nrinstall -f ~/nrtest
Once the install has completed (it may take some time), you can navigate to the data sub-folder and work with Node-RED as normal (e.g.
You may wish to adjust the
settings.js file and install any required Nodes at this point.
npm run to see the run commands available for your convenience. They are detailed in the README.md file installed in the data subfolder.
These instructions should work on any platform supported by Node.JS.
Table of Contents
I've used it now for a few years to create a custom home automation system and was impressed enough to start trying to give back to the community.
However, I've never personally quite liked the default installation. Don't get me wrong, it is great for beginners and for people inexperienced with the command line. But for production use and for security, I think that there is a better way to install and maintain your Node-RED systems.
In particular, Node-RED itself (and the companion node-red-admin module) are normally installed globally.
Not only can this open up security issues by having complex, inexperienced user generated code running under a global service, it also makes some of the files under the surface difficult to find on the odd occasions you need to.
There seems to me to be an easy solution to the global installation issue. This approach is more complex to set up normally since you don't, of course, get any hand-holding to set it up. And so the idea for this code came about.
The concept is really very simple.
- Create a folder in some convenient location.
- Use the
npmpackage manager to install node-red (and node-red-admin if you like) into that folder.
npm install --unsafe-perm --production node-red node-red-admin
- Create a sub-folder as your
userDir- the place all of the nodes and your flows and other information is put.
- Create startup and update scripts both for the master folder and the userDir folder using the script facility of npm.
You will find examples of these in the
templatesfolder of this repository.
Having a script to do this means that you can install Node-RED anywhere you like. Install two copies, ten if you want. Have different versions of Node-RED running in parallel. All really easy.
This works on any platform that Node-RED will run on.
The advantages of this approach I believe are:
- You can have as many different versions of Node-RED installed as you like making it easy to compare behaviours.
- Everything is in one place which makes backup and restore (including a known, working version of Node-RED itself) really simple.
- Everything is in a place that you have chosen. No wasted time hunting for folders in weird places.
- Users don't need admin rights to install an instance of Node-RED.
When using this method, uou can start Node-RED manually from either the master or the data folder by simply typing:
> npm start
The start script tells Node-RED of the correct userDir folder (the
data sub-folder). You can also use the
start script with any other method you may wish to use of starting Node-RED (Windows Scheduler, systemd, PM2, nodemon, etc.)
Updating Node-RED and installed nodes
If you have installed the two
package.json files in this repository, you will find that they contain
npm run ...
scripts such as
update-data. These scripts do everything necessary to see if anything needs
updating (reporting back to the console) and actually doing the updates correctly.
So from either the master or the data folders:
npm run check-masterchecks the master folder to see if either the
node-red-adminpackages need updating.
npm run update-masterreinstalls both
--unsafe-permparameter for Node-RED.
It does a reinstall rather than an update as, in the past, things like the serialport dependencies have failed unless you do a full reinstall (mainly after updating NodeJS itself to a new version).
npm run check-dataand
npm run update-datacheck and update any outstanding nodes and other packages you may have installed.
Each of the two package.json files also has a simple
update run script that applies to the corresponding folder.
If you lose track of the script names, simply run
npm run to get a list.
Please see the CHANGELOG file.
Please see the TODO file.
- NodeJS. v10 is the minimum supported version.