ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Large Node-RED flows become hard to read and maintain. Subflows offer a built-in way to encapsulate repeated logic, but they come with trade-offs around debugging and context isolation.
A decision guide for Node-RED context persistence: when localfilesystem storage is the right choice for single-instance restart survival, and how to configure and validate it safely.
Default Node-RED context lives in memory and vanishes on restart. Learn how to evaluate file-based versus in-memory stores for stateful flows, with a counter example and verification steps.
Learn how to build a minimal, secure Node‑RED flow that ingests MQTT sensor data into a time‑series database, with guidance on trust boundaries, operational checks, failure modes, and when to redesign.
Persist Node‑RED state locally with built‑in file context storage: requirements, design, trust boundaries, operational checks, failure modes, and when to upgrade.
Learn how to create, configure, and reuse Node-RED subflows so that updates propagate automatically across all instances, with a worked example and notes on limitations.
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.
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.
Learn how to pick file, Redis, or in‑memory context storage for Node‑RED flows based on persistence, scalability, and setup effort.
nodered
git
redis