Using Windows 10:
In experimenting with Node-Red I've been able to create several flows, and exported as .json files to a folder.
To execute I have a short-cut saved that starts a .cmd (command file) that starts the Node-Red server. Next I click on a short cut [http://127.0.0.1:1880/#flow/403537834f4eaadf] that launches a browser, and the URL field changes to [http://127.0.0.1:1880/#flow/bb1ef1dfee14acb5] and displays the last flow I was working on.
How do I have Node-Red load any of the other flows I've exported instead of reloading the last one I was working on. The only way I've found is to delete all the tabs of the last flow, and import the one I want to work on; surely this can not be right.
I've tried using the command prompt and typing in Node-Red flows.json|{my project name.json}; but I get Node-Red not recognized response.
Is there anyway to create a windows short-cut for each JSON file that will launch in the browser for editing when the server is running?
There's got to be a simple way to edit selected files.
As I mentioned when I try to run node-red in a command window it says;
'node-red in not recognized as a internal or external command, operable program or batch file.'
I found the folder ...../npm, where various node-red files are located; including "node-red.cmd".
When the command file is run the server is started. I was then able to get the basic node-red editor loaded in a browser. I began entering flows in the editor; the only way I found to save them was "Export all flows" to a .json file. I saved the browser URL so I could re-launch it after starting the server.
I suspect something went wrong with the installation in windows, but the same thing happened on another PC.
I found the folder ...../npm, where various node-red files are located; including "node-red.cmd".
When the command file is run the server is started. I was then able to get the basic node-red editor loaded in a browser. I began entering flows in the editor; the only way I found to save them was "Export all flows" to a .json file. I saved the browser URL so I could re-launch it after starting the server.
I suspect something went wrong with the installation in windows, but the same thing happened on another PC.
I did this maybe 6 months ago, but I believe I followed the installation instructions in the Node-Red guide.
It did install the folder referenced ...'npm. That folder was buried in hidden windows files under "user/appdata/Roaming".
The command file I used to launch the server was in "npm".
BTW: The installation also created entries in the Windows Start menu for Node.js as various related files command file references including an Uninstall Node.js.
Unfortunately, I can't get passed "GO", Node-Red is not recognized as a command or program using the command window. That's what makes me suspicious that the installation is incomplete.
Any suggestions as to how to correct the installation?
node-red is a convenience script and unless windows is correctly configured, the system won't find it.
If you know where red.js is, you can simply node /path/to/red.js. To avoid future issues, once you've worked out the start command you want, put a "start" script in ~/.node-red/package.json then you can do
cd ~/.node-red
npm start
Noting that the ~ shortcut only works in PowerShell, cmd prompt uses different shortcuts.