- docs
- FlowFuse User Manuals
- Using FlowFuse
- Getting Started
- FlowFuse Concepts
- Changing the Stack
- DevOps Pipelines
- Environment Variables
- FlowFuse File Nodes
- FlowFuse Persistent Context
- FlowFuse Project Nodes
- High Availability mode
- Instance Settings
- Logging
- Shared Team Library
- Snapshots
- Teams
- FlowFuse API
- Migrating a Node-RED project to FlowFuse
- Device Agent
- Device Agent
- Hardware Guides
- FlowFuse Cloud
- FlowFuse Cloud
- FlowFuse Self-Hosted
- Installing FlowFuse
- Overview
- Configuring FlowFuse
- DNS Setup
- Docker install
- Email configuration
- First Run Setup
- FlowFuse File Storage
- Install FlowFuse on Kubernetes
- Local Install
- Upgrading FlowFuse
- Administering FlowFuse
- Administering FlowFuse
- Administrator configuration for SSO
- licensing
- Monitoring
- Telemetry
- User Management
- Support
- Community Support
- Premium Support
- Debugging Node-RED issues
- Contributing
- Contributing to FlowFuse
# FlowFuse Persistent Context
Some Node-RED flows need a way to persist context values between restarts and FlowFuse stack updates but context data is ephemeral by default. With FlowFuse Premium, persistent context storage is possible and it survives restarts, upgrades and more.
# Usage
In your Node-RED, you will now have the option to store values in 2 context stores:
- Memory: This is for ephemeral context where you do not want it to be persisted.
- Persistent: This is for persistent context where you want values to persist restarts and upgrades.
FlowFuse provides 1MB of context storage per Node-RED instance.
For more information on Context, head over to the Node-RED Working with context guide.