![]() ![]() That would catch people out when moving between networks. Previously we left it unset, so the runtime would use the hostname to generate the flow file name. We’ve updated the default settings file to hardcode the flow file name to flows.json. You can see the new default settings file here. The settings are now in a better order, with clearer sections to help users navigate. More details Restructured default settings fileĪlong with the new node-red admin init command, we’ve reorganised the default settings file. You can run it using the node-red admin command: ![]() This makes it much easier to get started with a well configured, secure Node-RED environment. It asks you a series of questions about how you want to configure your Node-RED environment, such as setting up user security. We’ve added a new command-line option to node-red to help you generate a settings file. Runtime Features node-red admin init command Node-RED 2.0 does not support anything earlier than Node.js 12.17.x. Before we get to them, lets look at what’s new in the Node-RED core. These are optional plugins that really step up the developer experience within the Node-RED editor. We’re also releasing the first versions of the Node-RED Flow Debugger and Linter. As such, there are not a lot of big new features in this release - but there are certainly plenty of useful things to play with. ![]() This has required time and effort to do properly. This in turn has allowed us to make some major dependency updates internally. The main focus of this release has been dropping support for old versions of Node.js that are themselves no longer supported. The Change Log has the full list of changes in this release, but here are the highlights. If upgrading, please read the upgrade instructions. Node-RED 2.0 is now available to install. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |