FlowForge 1.2 is now available with single sign on and persistent context storage
Our final release for 2022 with some great new features to try out
Control access to FlowForge using single sign-on and retain context values when restarting projects.
We're pleased to announce version 1.2 is now available! The latest release of the FlowForge application contains new features, improvements, better documentation, and bug fixes.
We've put a great deal of work in this release to make it easier to run your own self-managed instance of FlowForge. That includes significant improvements for FlowForge in Kubernetes and Docker.
Keep reading for the details of what's in this release or you can watch our 1 minute roundup video of the new release above.
Single Sign-On Single sign-on (SSO) is a method of authentication that allows a user to access multiple applications or systems with a single set of login credentials, improving security, productivity, and user experience, and reducing IT overhead. We've implemented SSO using the Security Assertion Markup Language (SAML) framework. This allows users of FlowForge Cloud, Premium and the open source edition to easily access their FlowForge projects.
Persistent Context Node-RED provides a way to store information that can be shared between different nodes and flow executions without using the messages that pass through a flow. This is called ‘context’. You can now select if context should be stored in memory or in persistent storage. Persistent storage allows the stored values to be recalled after a restart of your project. You can see a demonstration of this feature on our Youtube channel.
In FlowForge 1.1 we added logging of user actions. In 1.2 we’ve improved the audit log interface to help you read the recorded user actions.
Configuring DNS for FlowForge has historically been challenging as for most FlowForge installs you'll need two entries. One for the FlowForge application, and one for the Node-RED projects. There's been updates to the documentation to make it much easier to set this up, and much faster. Please checkout the new documentation.
We've updated our documentation to always link to the latest build (older builds are still available).
Previously customers were asked to build their own containers for the main FlowForge applications, as well as the Node-RED ones. For the Node-RED containers this allows customers to pre-install packages in the container they intent to use. For FlowForge Cloud these containers are build by FlowForge. These containers are now published to the Docker Hub. This makes it much easier to get up and running with your first containers.
We are now pushing our Docker builds to Docker Hub, this saves users from having to build the Docker images when installing or updating. These containers are used by default by
Setting up MQTT for inter-project communication and communication with devices has been simplified. Please read the improved the documentation around configuration of MQTT.
# Bug Fixes
We've fixed the following bugs in this release.
Unable to edit 'Prevent Install of External nodes' template option #1376
Self-managed FlowForge needs an external email server to deliver email to users. FlowForge should be able deal with the email server being offline and gracefully recover once it is back online. #1159
Duplicate Activity Log for Project whose state is in flight #1461
We'd like the thank the following for their contributions to this release:
flecoufle for their work on #59
sumanpaikdev for their work on #53
sdirosa for their work on #1326
As an open-source project, we welcome community involvement in what we're building. If you're interested in contributing, checkout our guide in the docs.
# Try it out
In 1.2 we've continued to improve the experience of running your own self managed FlowForge installation. We're confident you can have self managed FlowForge running locally in under 30 minutes. You can install our local build, through Docker, or Kubernetes.
If you'd rather use our hosted offering: Sign up for FlowForge Cloud with the coupon FF12 to get your first project free for a month.
# Upgrading FlowForge
FlowForge Cloud is already running 1.2. To use persistent context you'll need to upgrade your projects stack.
If you installed a previous version of FlowForge and want to upgrade, our documentation provides a guide for upgrading your FlowForge instance.
# Getting help
Please check FlowForge's documentation as the answers to many questions are covered there.
If you hit any problems with the platform please raise an issue on GitHub. That also includes if you have any feedback or feature requests.
Chat with us on the
#flowforge channel on the Node-RED Slack workspace.
You can raise a support ticket by emailing email@example.com.
We've also added a live chat widget to our website, you can access it using the icon on the bottom right corner of our website. We'd love to hear from you.
- Use any npm module in Node-RED
- Bringing High Availability to Node-RED
- Node-RED Tips - Dashboard Edition
- Node-RED Community Survey Results
- Persisting chart data in Node-RED Dashboards