FlowForge 0.7 released

Rollbacks, Device Environment Variables and a FlowForge Theme

| Sam Machin

< Back to Blog Posts

Rollback projects to a previous snapshot, improvements in using Devices, and more.

Keep reading for the details of whats in this release our you can watch our 1 min roundup video of the new release above.

We're pleased to announce version 0.7 is now available. the next release of the FlowForge application.

Features

Rollback FlowForge is about running Node-RED at any scale, part of that scale is having multiple users collaborate on the same project. When you are collaborating with people it's important to be able to go back in time to a known working state. As part of that we are introducing rollbacks, this means that you can now take a snapshot of your project at a point in time and then make changes safe in the knowledge that you can rollback to that previous snapshot if you need to.

Device Environment Variables In the last release we introduced the concept of devices. We're already learning from how these are used and one feature we've added in 0.7 is Device Environment Variables. You have been able to set Environment Variables at the project level but when deploying a snapshot to multiple devices you may want to override these values for each device, for example to set a site ID. With device specific variable users are enabled to differentiate based on the context in their flows.

FlowForge Theme Now that we have a stronger visual identity in the Forge application we have continued that work through to the Node-RED editor. If you create or upgrade a project with a Node-RED 3.0 stack you will see a different theme in the editor. It's still very much Node-RED but just has some subtle hints to tie it back to the FlowForge application. We will continue to iterate on this to further integrate the experience between FlowForge and Node-RED in both directions.

ProjectTypes The introduction of ProjectTypes is a way to group Stacks together that share common characteristics - such as memory/cpu limits, or the availability of particular features. In platforms with billing enabled, such as our own FlowForge Cloud, the ProjectTypes can have different price points set on them. Within FlowForge Cloud, you'll see we've introduced the Small ProjectType - which applies to all existing projects on the platform.

Stack Versions This allows an admin to link different stacks together in their lineage. This allows administrators to nudge users to new Node-RED versions or upgrade pre-installed dependencies when running in a container environment. Any users with projects on an old version will be prompted that there is an update available, making it even easier to stay up to date with Node-RED versions when you build your flows on FlowForge.

Improvements

We've made a number of improvements to the overall experience of running FlowForge.

  • The Team Switch menu has been moved to a more prominent position in the interface, this also makes it easier to see how to create a new team. #616
  • Notifications have had an overhaul, you will now see waiting invites on all pages. #515
  • If you are running your own copy of FlowForge you can now see the version details in the admin pages #655
  • Device polling is no longer an INFO level message filling the log on your devices #10

Bug Fixes

We've fixed the following bugs in this release.

Upgrading FlowForge

FlowForge Cloud is already running 0.7 - ready for you to try out rollbacks and the new theme.

If you installed a previous version of FlowForge and want to upgrade, our documentation provides a guide for upgrading FlowForge on a local server.

Getting help

If you hit any problems with the platform, or have questions to ask, please do raise an issue on GitHub. That also includes if you have any feedback or feature requests.

Customers of FlowForge Cloud can raise a ticket by emailing support@flowforge.com

We also have a #flowforge channel on the Node-RED Slack workspace.

Sign up for updates