- docs
- Overview
- Administering FlowForge
- Contributing to FlowForge
- FlowForge API
- FlowForge Cloud
- Using FlowForge
- Changing the Stack
- devices
- Environment Variables
- FlowForge Concepts
- FlowForge File Nodes
- FlowForge Persistent Context
- FlowForge Project Nodes
- Instance Settings
- Logging
- Migrating a Node-RED project to FlowForge
- Node-RED Tools plugin
- Shared Team Library
- Snapshots
- Staged Deployments
- Teams
- Running FlowForge
- Installing FlowForge
- Configuring FlowForge
- DNS Setup
- Docker install
- Email configuration
- First Run Setup
- FlowForge File Storage
- Install FlowForge on Kubernetes
- Local Install
- Upgrading FlowForge
# FlowForge Persistent Context
Some Node-RED flows need a way to persist context values between restarts and FlowForge stack updates but context data is ephemeral by default. With FlowForge 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.
For more information on Context, head over to the Node-RED Working with context guide.