Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/blog/2022/06/community-news-05.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ If you've got something that you'd like us to share please email [contact@flowfu
We've had two releases since our last newsletter, there are a lot of related features between them.
We introduced a new design for the forge application which aligns with the branding on our website.
We've added [Devices](/docs/user/concepts/#device), allowing you to run and manage your Node-RED projects on your own hardware, this is ideal for applications that need to connect to either sensor data or specialist hardware deployed outside the cloud.
We added a new concept as part of this work, [Snapshots](/docs/user/concepts/#instance-snapshot) allow you to take a point in time copy of your project, today that can then be deployed to one or more devices but we have plans to expand this concept for things like [rolling back](https://github.com/FlowFuse/flowfuse/issues/587) a project to a previous point in time.
We added a new concept as part of this work, [Snapshots](/docs/user/concepts/#snapshot) allow you to take a point in time copy of your project, today that can then be deployed to one or more devices but we have plans to expand this concept for things like [rolling back](https://github.com/FlowFuse/flowfuse/issues/587) a project to a previous point in time.
[0.5](/blog/2022/05/flowforge-05-released/) Introduced the capabilities of copying a project or certain parts of it, allowing for scenarios like having multiple environments for Development and Production.

[Node-RED 3.0.0-beta-3](https://discourse.nodered.org/t/node-red-3-0-0-beta-3-released/64027)
Expand Down
2 changes: 1 addition & 1 deletion src/blog/2023/03/terminology-changes.md
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,7 @@ In future releases, environment variables will also be able to be stored at the

FlowFuse can also be used to manage remote Node-RED instances. This is typically useful when you have a number of remote devices that are required to run the same Node-RED instance, and may have variation in configuration or environment variables for example.

Devices are registered to an Instance, and can be configured to run [Snapshots](/docs/user/concepts/#instance-snapshot) of the Instance running in FlowFuse.
Devices are registered to an Instance, and can be configured to run [Snapshots](/docs/user/concepts/#snapshot) of the Instance running in FlowFuse.

To accomplish this remote management capability, the [FlowFuse Device Agent](https://github.com/FlowFuse/device-agent) needs to be installed on each device. Devices are registered with a Team, and then the appropriate device(s) are assigned to a Node-RED instance that should be deployed to the device(s). When the Node-RED instance is ready for deployment, a user creates a snapshot of the instance and marks it as a target snapshot for the device.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ Creating snapshots in FlowFuse is straightforward and can be done in just a few

### Creating Snapshots for Cloud and Device Instances

Before we begin, it’s essential to understand the differences between a cloud instance and a device instance. For more information, refer to the [Documentation](/docs/user/concepts/#what-is-the-difference-between-an-instance-and-a-device%3F).
Before we begin, it’s essential to understand the differences between a cloud instance and a device instance. For more information, refer to the [Documentation](/docs/user/concepts/#instance).

Additionally, let’s discuss the two types of device assignments available in FlowFuse:

Expand Down
2 changes: 1 addition & 1 deletion src/blog/2024/10/exploring-flowfuse-sbom-feature.md
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ To support the effective monitoring and assessment of your dependencies, FlowFus

### Accessing FlowFuse SBoM Interface

The Software Bill of Materials (SBoM) interface is available at the application level. For more information on the application, refer to the [Documentation](https://flowfuse.com/docs/user/concepts/#application). To access it:
The Software Bill of Materials (SBoM) interface is available at the application level. For more information on the application, refer to the [Documentation](/docs/user/concepts/#application). To access it:

1. Navigate to your Node-RED application within the FlowFuse platform.

Expand Down
2 changes: 1 addition & 1 deletion src/changelog/2024/02/instance-auto-snapshots.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,4 +12,4 @@ Two weeks ago, we introduced [auto snapshots for devices](/changelog/2024/02/dev
Whenever you deploy a change to the flows, a snapshot will be taken automatically. We'll keep the last 10 auto-generated snapshots on a first-in, first-out basis. Older auto-generated snapshots will be automatically cleaned up for you - unless
they are marked as a target snapshot for your devices.

Click the following links to learn more about [instances](https://flowfuse.com/docs/user/concepts/#instance) and [snapshots](https://flowfuse.com/docs/user/snapshots/#snapshots).
Click the following links to learn more about [instances](/docs/user/concepts/#instance) and [snapshots](/docs/user/snapshots/#snapshots).
Loading