- 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
# Staged Deployments
In FlowForge it is possible to configure a DevOps pipeline for your Node-RED instances.
- Navigate to your Instance and click on the "Settings" option.
- Select the "DevOps" tab
- Select the relevant instance from the "Target Instance" dropdown that is the next stage in your pipeline. For example, if your current instance is "My Application - Dev", your target instance could be "My Application - Staging" or "My Application - Production"
- Click the "Push to Stage" button, and confirm that you are happy to push over the relevant contents to your target instance
- You should see a confirmation alert to say this push has been successful.
- From here, you can click the "View Target Instance" button, to navigate straight to the Instance Overview of your Target Instance.
- The Target Instance will be in an "importing" state for a short while, and will then automatically restart itself with the relevant updates applied
Environment Variables - When pushing to a next stage, only your environment variable keys will be copied over. Values must be set on your Target Instance explicitly.
Instance Settings - None of your Instance Settings will be copied over (e.g. Editor, Palette or Security Settings).
This ensures a split between your staging environments.