- docs
- FlowFuse User Manuals
- Using FlowFuse
- Getting Started
- Static asset service
- Bill of Materials
- FlowFuse Concepts
- Changing the Stack
- Custom Hostnames
- Device Groups
- DevOps Pipelines
- Environment Variables
- FlowFuse Assistant
- FlowFuse File Nodes
- FlowFuse Persistent Context
- FlowFuse Project Nodes
- High Availability mode
- HTTP Access Tokens
- Instance Settings
- Logging
- Shared Team Library
- Snapshots
- Team Broker
- Teams
- User Settings
- FlowFuse API
- Migrating a Node-RED project to FlowFuse
- Device Agent
- Device Agent
- FlowFuse Device Agent Introduction
- Quick Start
- Installation
- Quick Start with Web UI
- Register your Device
- Running the Agent
- Deploying your Flows
- Hardware Guides
- FlowFuse Cloud
- FlowFuse Cloud
- FlowFuse Self-Hosted
- Quick Start
- Installing FlowFuse
- Overview
- Configuring FlowFuse
- DNS Setup
- Docker install
- Docker from AWS Market Place
- Docker on Digital Ocean
- Add Project Stacks on Docker
- Docker Engine on Windows
- Email configuration
- First Run Setup
- FlowFuse File Storage
- Install FlowFuse on Kubernetes
- Upgrading FlowFuse
- Administering FlowFuse
- Administering FlowFuse
- Configuring Single Sign-On (SSO)
- Licensing
- Monitoring
- Telemetry
- User Management
- Support
- Community Support
- Premium Support
- Debugging Node-RED issues
- Contributing
- Contributing to FlowFuse
- Introduction
- Adding Template Settings
- API Design
- Creating debug stack containers
- Database migrations
- FlowFuse Architecture
- Local Install
- State Flows
- Device Editor
- Invite External Users
- User Login Flows
- Reset Password Flow
- Project Creation
- Instance states
- User Sign up Flow
- Team creation Flow
- Team Broker
- Working with Feature Flags
# FlowFuse File Nodes
Node-RED instances running within FlowFuse Cloud with Launcher version before 2.7.0 include a modified set of nodes that make it possible to store files safely regardless of the environment. Cloud based instances can read and write to persistent storage using these nodes. Edge devices will store files on its local filesystem.
There are two nodes in the File Node collection:
file- A file node for writing to persistent storagefile in- A file node for reading from persistent storage
# FlowFuse 2.7.0 and later
With the release of FlowFuse v2.7.0 a new Persistent Storage feature was enabled.
This allows the default Node-RED File Nodes to work safely by mounting a volume to ensure files are persisted across all restarts of the Instance.
On Docker, Kubernetes self hosted instances and FlowFuse Cloud the volume is mounted on /data/storage. The Current Working Directory for the Node-RED process is set to this directory, this means that if you do not specify a path in a node it will created or read from this directory.
For LocalFS builds a storage directory is created in the Instance User Directory, this means that if FlowFuse is installed in /opt/flowfuse the directory will be at
/opt/flowfuse/var/projects/<project-id>/storage
# Templates
On FlowFuse Cloud before v2.7.0 the Default Template had an explicit exclusion for
10-file.js to ensure that the replacement FlowFuse File Nodes were loaded. This Template was renamed to "Default v1" to differentiate it. If your instance is using this version of the template then it will need modifying to allow access to the default Node-RED File Nodes to make use of the new Persistent Storage. Please contact FlowFuse support to arrange this, they will also be able to migrate any files stored in the old service.
# Usage
Simply drop the file nodes into your flows as you would with the regular file nodes in Node-RED.
Example: Write string to a file, then read from the file
There are more helpful built-in examples on the Import Examples dialog in Node-RED.
# Deployment Considerations
When a snapshot is deployed to a device, the original Node-RED file nodes are used and any files will be stored on the device's local filesystem.