In this article I’m going to show you how to install a Server that includes optional advanced capabilities, that are not available by default with the standard installs mentioned in Node-RED’s . Node-RED documentation If you’re following my series, you’ll know that my intention is to teach you how to use Node-RED as a tool for business app development and integration, instead of just home automation and hobby-based projects. To achieve this, we cannot set up Node-RED the traditional way, which is installing it as a global module on our local machine. We need more control and flexibility. For example: Up and Running with Node-RED To run multiple instances of Node-RED To containerize and deploy to various on-prem and cloud environments To integrate with 3rd party services Everything needs to be achievable from one Node-RED instance, and today’s install will give us just that. Watch Video On YouTube Node JS and NPM Required To start, you need to have at least Node JS or higher installed on your machine. If you have an older version or don’t have installed, I highly recommend using a Node Version Manager to be able to install one or multiple versions of Node. There are many great Version Managers out there, but for an immediate recommendation, is one that we at use and it works very well. Not only will you be able to easily switch between various versions of Node, but NVM also takes care of permission issues on your Operating System that sometimes occurs when installing Node directly. 12.18 Node NVM Agilit-e Find “agilite-node-red” on GitHub Now, the boilerplate Node-RED server we’re going to be using can be found on GitHub and is called . This repo is maintained by the team at and provides the control and flexibility mentioned earlier. agilite-node-red Agilit-e Download Relevant Version Once the boilerplate repo is open in your browser, switch the branch from Master to . This is the current boilerplate version as per the release of this article, is compatible with and runs . Should you be reading this article long after it was released, you can switch to newer branches that will support upgraded versions of Node and Node-RED. Reference the file for these versions. 7.3.1 Node 12.18, Node-RED 1.3.4 README Once you’ve switched to branch , click on the button, following by clicking on to download the boilerplate to your local environment. One downloaded, extract the zip file, which will extract the boilerplate to a folder called . 7.3.1 Code download zip agilite-node-red-7.3.1 Install Node Modules Via your Terminal or Command Prompt, navigate to the boilerplate folder and run the following command . This installs the main project dependencies based on the file and ignores the dev dependencies which you don’t need. This ensures the boilerplate’s node modules are installed the way we intended, to avoid possible inconsistencies and problems. npm ci — only=production package-lock.json Once the NPM install is complete, enter the command . This starts up the Node-RED server, which you can now access by opening your preferred web browser and entering the URL: . If all was successful, you will see the open in your browser’s window. You are now ready to start using Node-RED. npm run main http://localhost:6020 Node-RED Editor Closing As mentioned before, this boilerplate offers everything of Node-RED and more, which I’ll be taking everyone through step by step in my series. So if you haven’t yet, be sure to subscribe to my , or alternatively follow me on this site. In the meantime though, I welcome you to peruse the configuration for this boilerplate, which can be found in the folder, in a file called . This is where much of the magic happens, but more on that very soon. Up and Running with Node-RED YouTube channel config/templates default-config.json Until next time though…cheers :) Also published on Medium's johnjardin

YouTube

Join me on my BleedingCode YouTube Channel

Node-RED Configuration Explained In 600 Words

Too Long; Didn't Read

Company Mentioned

@johnjardin

RELATED STORIES