[ANNOUNCE] Node-RED Desktop v1.0.0 Released

Hi all,

I released Node-RED Desktop v1.0.0 .

New features

  • Debug out
    This function enables you to debug flow without putting debug nodes.
    So you can debug also existing flow without modifying and deploying flow.

    • This function hooks output of all nodes and send msg into debug window.
    • To use this, switch on from the menu [Extend]-[Debug out]
  • Vertical flow (experimental)
    You can ease to try vertical flow without building it yourself.
    (This is a experimental version. This specification will change in future)

If you have interested in Node-RED Desktop, Please try it.

Regards,

sakazuki

What is Node-RED Desktop

Node-RED Desktop is a desktop application of Node-RED for windows/mac.

You can

  • easily setup Node-RED on your desktop.
    • with one click installer and auto updater
  • quickly create and discard a flow many times.
    • with standard file menu.
  • easily publish the public HTTP endpoint and integrate with cloud services.
    • with embeded ngrok.
  • easily create a custom node
    • with node-red-nodegen, and bundled npm commands

And also,

You can use almost all powerful and useful Node-RED features

6 Likes

I've been using Node-RED Desktop since release 0.9.0 and I'm very happy with the nice implementation.

@sakazuki Thank you very much for sharing this useful project!

I have a strange problem
If I use Node-RED desktop (with Listen Port set to 1881) to run a simple webserver, it is not accessible using the machines IP address

[{"id":"82b8b3e7.002aa","type":"http in","z":"c0716222.d526f","name":"","url":"/translate","method":"get","upload":false,"swaggerDoc":"","x":230,"y":240,"wires":[["b0219c6a.7be57","fdbf17de.e30a88"]]},{"id":"f452fb6d.41c4d8","type":"http response","z":"c0716222.d526f","name":"","statusCode":"","headers":{},"x":890,"y":200,"wires":[]},{"id":"b0219c6a.7be57","type":"debug","z":"c0716222.d526f","name":"","active":false,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","x":590,"y":320,"wires":[]},{"id":"fdbf17de.e30a88","type":"change","z":"c0716222.d526f","name":"","rules":[{"t":"set","p":"payload","pt":"msg","to":"{\"result\":\"OK\"}","tot":"json"}],"action":"","property":"","from":"","to":"","reg":false,"x":620,"y":200,"wires":[["f452fb6d.41c4d8"]]}]

e.g
192.168.0.23:1881/translate or win8:1881/translate (win8 is machine name)
gives

both localhost and 127.0.0.1 work

image

If I run the same flow on my normal Node-RED instance - it works fine

image

I'd be interested is someone else could try this out and see what happens

Note: It doesn't matter what port is used - the fault occurs even if the Listen Port is not set

hi

NRD default listen on 127.0.0.1.
This is a spec for security.

To publish to local network, you need to set NRD_LISTEN_IP .

please see detail in wiki

regards