Anyone, this seemed to be a promising start to the issue ?
Nothing "happend" ... unfortunately.
It's still waiting to be reviewed by the Node-RED team. Very likely not on any priority list...
1 Like
Shall we open a new thread to resurrect this?
As it happens, I've just reset a bunch of Windows 10 and 11 devices so I currently do have clean test machines available.
Very welcome. I just checked the installer yesterday ... and it didn't show any issues handling the latest NR version.
Looking forward to your feedback ... and those of others.
So it seems we need some volunteers to do some testing?
@knolleary, @Steve-Mcl, is something needed to look at getting the installer adopted?
Where can we find the installer?
I might be in a position to try this out over the coming weeks.
To save me hunting it down, can you link to the issue/repo please?
Already in the node-red github. 
Ralph is the original author of course.
Very slick.
I only did a quick test as my dev pc is my bread and butter and I dont have another win installation to test against at this time.
I did a non global install, kept current nodejs version, chose NR 4.0.8 and it worked a charm, downloading the node_modules to the specified directory. However, i chose not to add an icon to desktop. I looked in the chose directory hoping to see a "launch.cmd" (or similar) for me to run but there was none. I did re-run the setup this time i chose to create a desktop icon, but it did not make one.
I then did another run, this time adding a 2nd install (this was not super obvious). This time I chose to create a desktop icon & it worked (sorta). Upon launching the desktop icon it started a command window and fired up Node-RED but it was using the settings file from my HOME/.node-red installation (not the custom installation).
I could have sworn that if the userDir is specified it would be enough to tell node-red to use the settings file from that location* but alas, it uses the one from ~/.node-red. I tested this with NR 3.0.2 and the same thing occurred.
* docs for CLI: Running Node-RED locally : Node-RED
-s,--settings FILESets the settings file to use. Default:settings.jsinuserDir
Perhaps this is a Node-RED bug?
This is what happened...
Welcome to Node-RED
===================
25 Jan 15:55:37 - [info] Node-RED version: v4.0.8
25 Jan 15:55:37 - [info] Node.js version: v18.20.2
25 Jan 15:55:37 - [info] Windows_NT 10.0.22631 x64 LE
25 Jan 15:55:38 - [info] Loading palette nodes
flowfuse-nr-utils added
25 Jan 15:55:39 - [info] Settings file : \Users\me\.node-red\settings.js <<< Unexpected
25 Jan 15:55:39 - [info] HTTP Static : c:\staticFiles > /static/ <<< from my ~/.node-red settings file!
25 Jan 15:55:39 - [info] Context store : 'default' [module=memory]
25 Jan 15:55:39 - [info] Context store : 'file' [module=localfilesystem]
25 Jan 15:55:39 - [info] User directory : C:\test\node-red
25 Jan 15:55:39 - [warn] Projects disabled : editorTheme.projects.enabled=false
25 Jan 15:55:39 - [info] Flows file : C:\test\node-red\flows.json
25 Jan 15:55:39 - [info] Creating new flow file
I would suggest the following tweaks:
- the start up shortcut specifies
.node-redas theuserDir- This keeps the node-red installation and the "project" in distinct directory
- the installer generates the default settings file in
chosen-dir\.node-red\settings.js - the start up shortcut adds
--settings .node-red/settings.js - Create a launcher shortcut in the specified dir (always) (regardless of whether the user ticked "Generate desktop icon") - a nice touch would be if the installer could inform the user of this in the last step summary?
- Decorate the launcher shortcut in some way? Perhaps use the port number or the parent dir name? (e.g. "Node-RED:1887")
- Helps to differentiate multiple installs.
Other points of note:
- NodeJS v22 was not an available option.
- Installing as a service would be a nice touch (NSSM? PM2? Other?)
- however that brings another world of hurt like which account to run the service as, system global locations, permissions etc.
All in all though, super promising.
Great simplification. 
When I get the chance to try this out on a fresh win 11, I will feedback on that.
2 Likes
