Enable projects

Node-RED
1

EPIC system 4.0.2-b.194 firmware,
Running Node-Red 4.02
node.js v20.12.2

Does this feature work yet?

1 Like
2

Hi James, We announced the official release of EPIC Firmware 4.1.0 today . Updates to Node-RED include: v4.1.3, with the underlying Node.js runtime updated as well (v22.22.0).

For more information please reference today’s OptoBlog post: New groov EPIC and RIO firmware 4.1.0 available now

1 Like
3

Hi James, it requires shell access and has only been partially tested on groov, but yes, it can be enabled and has been working for me. Here’s how I set it up in SSH:

  • Use sudo to edit the Node-RED settings file (as root):
    sudo nano /usr/share/nxtio/services/node-red/settings.js
  • Add the projects configuration JSON to modules.export:
    editorTheme: {
        projects: {
            enabled: true
        }
    },
  • Save the file and restart Node-RED.
  • Next time you open or refresh the Node-RED editor you will get a pop-up prompting you to create your first project, then you can access the projects menu using the dropdown in the top right.

I’ll leave it at just those instructions for now while I continue experimenting on my end. Please let us know if that does or doesn’t work for you and what your experience is.
If I come across any issues or anything else of interest I’ll update this post / thread.

1 Like
4

Thanks Terry,
The latest release of OPTO22 EPIC firmware (4.1.0) cited by JeffS might already include that change in settings.js. This question is in conjunction with an effort to implement GIT and I see that the update includes something about Ignition and GIT.

Thanks Again!

Jim

5

Just a heads up that the Node-RED implementation on groov EPIC and RIO is always 100% unmodified.
However NR is set up by default is how it will be on groov; any modifications to the settings.js file will need to be done manually. So things like file storage of context variables, editor themes, external modules for function nodes, and projects all require modifications to settings.js which must be done with root permissions via SSH.

Just something to be mindful of when experimenting with Node-RED on groov.

6

Thanks Terry, Good info!

7

Thanks Terry, (sorry for multiple edits of this reply)
We have an off-site file server and are running 7 epic systems with lots of Node-RED flows.
I edited the settings.js file to insert the snippet you cited above. (I also commented the flowFile line so the system will write flows to the filename flows_hostname.json. Note: when you change the filename the editor will not be able to find/load existing flows - export all flows first and then import after you restart node-red.)

I created seven folders on the file shares for the 7 EPIC systems and created 7 repositories. Now it is all automated - when I deploy it goes into the local storage and from there I can stage and commit to the off-site repository.

1 Like