Hi There!
I’m Gerrit and I created this blog using Node-RED, mostly as an experiment.
Besides creating this blog in Node-RED, I also created FlowHub.org using Node-RED.
Node-RED Vitae
My largest flow codebase is FlowHub.org which is a platform for organising flow code. Using the Node-RED integration, I can then pull, compare and push my flow code all from within Node-RED.
FlowHub is my solution for organising and coordinating a large collection of interdependent flows. It underscores my Node-RED focus, exploring solutions to make Node-RED more accessible and usable for a broader audience:
ETL pipelines flow that I created to test out the idea of how simple it could be to create ETL pipelines in Node-RED. I ended up creating the streaming nodes package which uses the Stream API of NodeJS, something that isn’t yet integrated into Node-RED.
Deploying flows remotely so that I can create one flow that defines the complete configuration and setup of another Node-RED installation. An example of a visual deployment script.
I²C bus flow was a mini project to operate a LED display using Node-RED. The project demonstrates that visual code can appear like the task that it is solving. In this case, the flow appears as the LED display its controlling.
I have had a look into integrating AI into Node-RED. Here Node-RED acts as a talk-show host between two AI models trapped into a conversation.
All the flow links above are hosted by FlowHub.org, demonstrating another aim of FlowHub: to make flow documentation accessible. The documentation shown is stored in the flow using the tab description attribute of the flow.
My very first Node-RED project was Red-Back: Node-RED as a Backend - for those not familiar, a reference to Redback spiders. I was very proud of creating an API backend for a Python frontend which also resolved my initial Node-RED quandary: what to do with it if you don’t want to automate your home and you don’t work in an IIoT environment?
Contact: GitHub / LinkedIn / Node-RED forum / Email / vCard