Node Maker does not currently run under windows due to file path differences and commands. Currently there are two issues:
- The write node does not appear to be writing files. Not sure why.
- Restarting the node-red instance doesn't work because those commands are bash specific (Linux, maybe macos only).
The command to restart node-red relies on starting node-red from the CLI and writing a PID (process id) file to a temp folder. When invoking Node Maker, it should execute a command to restart node-red by terminating the prior process by PID and then restarting node-red (updating the PID file in the temp folder).
Research
The "Windows" way to do this would be to invoke PowerShell from cmd via a command like:
powershell.exe -Command "(Start-Process -FilePath node-red -PassThru -WindowStyle Hidden).Id"
This runs node-red in a hidden window and returns the process id. We can then use taskkill to end the process:
Implementing this could be possible; and we'd gain Windows support.
Node Maker does not currently run under windows due to file path differences and commands. Currently there are two issues:
The command to restart node-red relies on starting node-red from the CLI and writing a PID (process id) file to a temp folder. When invoking Node Maker, it should execute a command to restart node-red by terminating the prior process by PID and then restarting node-red (updating the PID file in the temp folder).
Research
The "Windows" way to do this would be to invoke PowerShell from cmd via a command like:
This runs node-red in a hidden window and returns the process id. We can then use taskkill to end the process:
Implementing this could be possible; and we'd gain Windows support.