Persist Node-RED flow state with local filesystem context
Use Node-RED built-in localfilesystem context to keep flow and global variables across redeploys without an external database.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Use Node-RED built-in localfilesystem context to keep flow and global variables across redeploys without an external database.
Learn how to configure Node-RED's file-based context storage so flow and global variables survive restarts. Includes a ready-to-use settings.js snippet, serialization rules, common pitfalls, and verification steps.
Learn how to encapsulate common functionality into Node‑RED subflows, see a JWT‑validation example, and understand the trade‑offs before adopting this pattern in your own flows.
Enable file-based Node-RED context storage so flow and global values survive restarts and redeploys.
Choose Change for simple property moves, JSONata for read-only transforms, and Function only for complex logic in Node-RED flows.
How to choose between Node-RED's memory, file, and Redis context stores, with a settings.js example and restart persistence test.
Stop copying and pasting nodes. Learn how to use Node-RED Subflows to encapsulate reusable logic, parameterize components with environment variables, and maintain a clean workspace.
Learn how to choose between memory and filesystem context storage in Node-RED to prevent data loss during restarts and flow deployments.
Stop copying and pasting node sequences in Node-RED. Learn how to use Subflows to encapsulate repeated logic, centralize updates, and reduce flow sprawl for more maintainable automations.