Node-Red
github.com
Node-Red
1–10 of 28 posts
Re: Node-Red
#2Should probably change the submission title to "Awesome Node-RED".
Re: Node-Red
#3Should probably change the submission title to "Awesome Node-RED".
Or "Curated list of useful resources for Node-RED", as the subtitle is on this page. Even "awesome node-red" doesn't really say anything about the content.
Re: Node-Red
#4Should probably change the submission title to "Awesome Node-RED".
Or "Curated list of useful resources for Node-RED", as the subtitle is on this page. Even "awesome node-red" doesn't really say anything about the content.
"Awesome X" is often used as a stand-in for "curated list of useful resources for X". Like Awesome Rust, Awesome ruby and so on.
Re: Node-Red
#5Earlier quoted context omitted.
Or "Curated list of useful resources for Node-RED", as the subtitle is on this page. Even "awesome node-red" doesn't really say anything about the content.
"Awesome X" is often used as a stand-in for "curated list of useful resources for X". Like Awesome Rust, Awesome ruby and so on.
I see. I was not aware of this, which is why I think it's a bad title :)
Re: Node-Red
#6Earlier quoted context omitted.
"Awesome X" is often used as a stand-in for "curated list of useful resources for X". Like Awesome Rust, Awesome ruby and so on.
I see. I was not aware of this, which is why I think it's a bad title :)
I am aware of it, and agree ;)
It's a bit like 'Polite Notice' - I'll decide how polite your notice is myself thanks!
Even if one word is desired, wouldn't 'ecosystem' be so much better? (I realise that's a corruption of its meaning, but it's a now widespread meaning anyway.)
Re: Node-Red
#7The one thing I want added to Node-Red is an editable, sanely git diff-able on-disk text format for its configuration. I want to be able to edit either in GUI or in text, and then view the result in the GUI (and have it work of course!).
Does anybody know if there's any plugin for or way of achieving that? When I last looked into it, people were checking in the config files (whatever format they were, perhaps proprietary) but they were a mess, may as well be binaries or PDFs etc. for all the value you'd get out of git for them.
Re: Node-Red
#8The one thing I want added to Node-Red is an editable, sanely git diff-able on-disk text format for its configuration. I want to be able to edit either in GUI or in text, and then view the result in the GUI (and have it work of course!). Does anybody know if there's any plugin for or way of achieving that? When I last looked into it, people were checking in the config files (whatever format they were, perhaps proprie…
The flows are stored as JSON and there is a setting to save them as prettified to make them more readable (`flowFilePretty: true` in the settings.js which is on by default in recent release).
Also the flow storage is fully plugable (https://nodered.org/docs/api/storage/) so nothing to stop you choosing/implementing a different storage format e.g. YAML https://github.com/natcl/node-red-contrib-yaml-storage
Re: Node-Red
#9Earlier quoted context omitted.
I see. I was not aware of this, which is why I think it's a bad title :)
I am aware of it, and agree ;) It's a bit like 'Polite Notice' - I'll decide how polite your notice is myself thanks! Even if one word is desired, wouldn't 'ecosystem' be so much better? (I realise that's a corruption of its meaning, but it's a now widespread meaning anyway.)
Isn’t the point of “polite notice” that it looks very much like “police notice” when glancing quickly? That is certainly how it is abused by horse riders on the road around here.
Re: Node-Red
#10The one thing I want added to Node-Red is an editable, sanely git diff-able on-disk text format for its configuration. I want to be able to edit either in GUI or in text, and then view the result in the GUI (and have it work of course!). Does anybody know if there's any plugin for or way of achieving that? When I last looked into it, people were checking in the config files (whatever format they were, perhaps proprie…
The flows are stored as JSON and there is a setting to save them as prettified to make them more readable (`flowFilePretty: true` in the settings.js which is on by default in recent release). Also the flow storage is fully plugable ( https://nodered.org/docs/api/storage/ ) so nothing to stop you choosing/implementing a different storage format e.g. YAML https://github.com/natcl/node-red-contrib-yaml-storage
But can you actually hand-write it? When I last looked IDs were UUIDs or similar, so you'd have to create a node in the GUI for a start, and even then the structure of it just clearly wasn't designed for manual editing or diffing. 'Storage' sort of sums it up really, doesn't it?