Hi everyone.
The other topic has closed with no answer, and I am opening again because I got the same problem.
I use node-red in Linux with no problem. The auto-boot using the official install script works flawless.
But in Windows, when I start node-red, the cmd terminal opens and stay. This is a problem because I can miss click and the terminal stop the node-red execution or simple miss-close the cmd window.
Is there anyway to auto-boot in Windows without the terminal window staying open?
Alternatively, you could fire up node-red via FlowForge where you will get a whole suite of tools to help you fire up 1 or more instances at the click of a button
I also use NSSM to run Node-red as a service, as @Steve-Mcl implied.
However, I only do this on production environment. When developing or testing, I use a command-line console, which allows me to see errors, aborts etc.
I was using the Windows Task Manager to run node-red. The terminal was showing everytime the system boots (minimized, but shows on taskbar).
I will try NSSM.
One more question:
From what I've been reading, using NSSM will still show terminal console, but setting the integer (REG_DWORD) HKLM\SYSTEM\CurrentControlSet\Services<service>\Parameters\AppNoConsole registry value to 1 will resolve this.