Node-RED full shortcuts listing and something else

[olai]

Hi! Hello all!

I am new to Node-RED, but have successfully installed it (and node.js, of course) both on an Ubuntu server and a Raspberry pi running Raspbian. I also got it working with some example code, so it looks promising.

I did some testing first, which broughtt me into trouble by always terminating the command "node red", until I found out that I could delete contents of ~/node-red-0.5.0/flows_raspberrypi.json, and thus get "node red" running to accept connection to raspberry-ip-addr:1880. Is there a more comprehensive documentation explaining how to do this correctly?

But my main question is: where is a more full listing of keyboard shortcuts than those found by pressing the button to the right of the Deploy button?

I have elsewhere found: CTRL+I for Insert in clipboard?

How do I stop a deployed stream? (Without altering the node setup!?)

How do I make only the stream on a particular sheet run?

Regards Kåre Olai   :-)

[Nicholas O'Leary]

Hi,

you can find our documentation here: http://nodered.org/docs/. Under the running section of the docs, it does talk about pointing at alternative flows files on start up. It doesn't explicitly talk about using that feature to point at a 'blank' flow in order to recover a crashing system. That said, _anything_ that causes node-red to crash is a bug and we would welcome bug reports on github or here.

The popup you get when you click 'Keyboard Shortcuts' from the menu (or when you press ?) is meant to be the full listing - Ctrl-I is listed on that. 

> How do I stop a deployed stream? (Without altering the node setup!?)

Node-RED runs the deployed flows. If you want to stop the flows you either deploy a blank flow to replace it, or you stop Node-RED running (ie, kill the node process).

> How do I make only the stream on a particular sheet run?

You cannot do this. We do not support partial deployments of what is in your workspace. It is all or nothing.

Cheers,

Nick

--
http://nodered.org
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-red+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[olai]

kl. 14:46:19 UTC+1 mandag 3. februar 2014 skrev Nicholas O'Leary følgende:

you can find our documentation here: http://nodered.org/docs/. Under the running section of the docs, it does talk about pointing at alternative flows files on start up. It doesn't explicitly talk about using that feature to point at a 'blank' flow in order to recover a crashing system. That said, _anything_ that causes node-red to crash is a bug and we would welcome bug reports on github or here.

Thanks alot for answers! Just need to learn the vocabulary and specialities   ;-)  Regretfully I blanked out the errored flowfile and node startup-info. I will come back for more....

Regards Kåre Olai