If we want to formalise this as something the project provides, the sooner we move it into the Node-RED org on GitHub the better imho. Is that something you're open to @ralphwetzel ?
In terms of the artwork, if I'm going to be picky about consistency with the project branding, it is missing the hyphen between the words and should use Roboto Slab as the font.
The default installation of NodeJS & Node-red on Windows is personalized, i.e. uses the user's home & AppData folders.
However, when we install on a project server, we do not want to rely on any specific user account, so tweak the NPM prefix & Node-red user directory into directories within ProgramData.
Is there a way to select the installation mode (personal/shared) in the installer?
That's a topic we definitely need to discuss.
Changing the NPM prefix impacts - as far as I understand the situation - the whole Node.js / NPM environment on a given Windows system. I have my doubts that this should be doable by an installer of a single product - even on request of a user.
I could imagine offering this yet as an option in the very narrow case of a clean system - when the installer detects that the NPM prefix is not defined.
@all: Any opinions on that - or alternative options?
@omrid Do you apply additional changes - that could be automated by the installer?
Your right path looks like the idea to support more than one installation of node-red on one Windows system.
How does this fit to the instruction in the docu to install node-red with the global flag?
Here is a more detailed version - probably pushing the abilities of the script at this point - but could be a guide into the type of interaction it will offer.
The "normal" approach on Windows appears to be to select to install for "All Users" instead of a single user. This uses the all users profile and requires local or domain administrator rights.