Version-Controlled Flows: Using Node-RED Projects with Git
Enable Node-RED Projects to put your flows under Git version control: setup in settings.js, creating and cloning projects, commit/push workflows, and recovery from bad deploys.
Loading…
ReadMeFeed / Community knowledge
Nodered
Real questions. Useful conversations. Find the people who know your stack.
Nodered
Developer tools · #nodered
gitUsing Node-RED Subflows to Keep Your Flows DRY and Maintainable
Learn how to turn a repeated group of nodes into a reusable subflow, expose configurable properties, and see the impact of changes across all instances.
Choosing a Context Storage Mechanism for Node‑RED Flows
Learn how to pick file, Redis, or in‑memory context storage for Node‑RED flows based on persistence, scalability, and setup effort.
redisReusing Logic in Node‑RED with Subflows
Learn how Node‑RED subflows let you encapsulate repeated MQTT‑function‑SMTP patterns into a reusable unit, with a worked temperature‑alert example and notes on debugging and versioning.
Persisting State in Node-RED Using the Local Filesystem Context Store
Learn how to use the localfilesystem context store in Node-RED to ensure your flow and global variables survive restarts and deploys.
A Function-Node Pattern for Safe MQTT Payload Transformation in Node-RED
A practical function-node pattern for Node-RED that validates MQTT payloads defensively, normalizes output, reports health via node status, and persists state across restarts — plus the event-loop limits you need to respect.
Using Node‑RED Subflows to Eliminate Duplicate Logic in IoT Pipelines
Learn how Node‑RED subflows let you package reusable node groups, expose ports, and keep every instance in sync—cutting maintenance overhead in IoT flows.
Selecting MQTT QoS Levels in Node-RED for Reliable IoT Messaging
Guidance on choosing QoS 0, 1, or 2 in Node-RED MQTT nodes, with trade‑offs, a comparison table, and a function‑node example for per‑message QoS override.
Node-RED Flow Debugging: A Diagnostic Guide for Silent Failures
Node-RED flows fail silently due to unmet dependencies or misconfigured credentials. Follow this diagnostic guide to identify and resolve common issues.