[{"data":1,"prerenderedAt":334},["ShallowReactive",2],{"blog-\u002Fblog\u002F2023\u002F02\u002Fflowforge-1-4-0-released":3,"blog-all-for-related":333},{"id":4,"title":5,"authors":6,"body":8,"cta":312,"date":313,"description":14,"extension":314,"image":315,"lastUpdated":312,"meta":316,"navigation":321,"path":322,"seo":323,"sitemap":324,"stem":325,"subtitle":326,"tags":327,"tldr":312,"video":331,"__hash__":332},"blog\u002Fblog\u002F2023\u002F02\u002Fflowforge-1-4-0-released.md","FlowFuse v1.4 with device provisioning in bulk and staged development process",[7],"ian-skerrett",{"type":9,"value":10,"toc":300},"minimark",[11,15,18,29,34,40,48],[12,13,14],"p",{},"Deploy Node-RED to many devices quickly, and allow a staged development process with the latest release of FlowFuse v1.4.",[12,16,17],{},"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.",[12,19,20,21,28],{},"To make it easy for everyone to experience FlowFuse, we are introducing a new free 30-day trial. You can now experience the power of using FlowFuse to quickly deliver Node-RED applications in a reliable, repeatable, collaborative, and secure manner. To get your free trial simply ",[22,23,27],"a",{"href":24,"rel":25},"https:\u002F\u002Fapp.flowfuse.com\u002Faccount\u002Fcreate",[26],"nofollow","sign up for FlowFuse Cloud;"," no credit card is required!",[30,31,33],"h2",{"id":32},"new-user-features","New User Features",[12,35,36],{},[37,38,39],"strong",{},"Automatic Device Provisioning",[12,41,42,43],{},"Most prominently, FlowFuse 1.4 features automatic device onboarding for fleets. Simply download a FlowFuse device provisioning credential to allow quick roll-out to a whole fleet, without the need to have device specific configuration. When the agent starts, the FlowFuse agent and the Node-RED snapshot will automatically be provisioned to the device and start operations. ",[22,44,47],{"href":45,"rel":46},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F1212",[26],"Issue #1212",[49,50,51,58,63,71],"div",{},[52,53],"lite-youtube",{"videoid":54,"params":55,"style":56,"title":57},"XTVw4O4-Crg","rel=0","width: 704px; height: 100%;","YouTube video player",[12,59,60],{},[37,61,62],{},"Support for Staged Development",[12,64,65,66],{},"A new feature of 1.4 is the ability to setup staged deployments. This makes it possible to simply move a project between a Development > Test > Production for your Node-RED application delivery. ",[22,67,70],{"href":68,"rel":69},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F1580",[26],"Issue #1580",[49,72,73,76,80,143,147,150,172,176,179,194,202,206,213,221,225,233,240,244,252,261,269,277,290,297],{},[52,74],{"videoid":75,"params":55,"style":56,"title":57},"6QOmotlrwWw",[30,77,79],{"id":78},"improvements","Improvements",[81,82,83,92,100,108,116,124,132,135],"ul",{},[84,85,86,87],"li",{},"It's now much easier to change the resources available to your Node-RED instance. With a few clicks a resource intensive workload can be processed faster by changing between small, medium, or large instance types. ",[22,88,91],{"href":89,"rel":90},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F595",[26],"#595",[84,93,94,95],{},"Last release allows users to capture flows in a shared library to reuse in another flow, now it's possible to preview the stored flows. ",[22,96,99],{"href":97,"rel":98},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F1657",[26],"#1657",[84,101,102,103],{},"Add a synchronous mode for the FlowFuse persisted context store, next to the asynchronous mode already available. ",[22,104,107],{"href":105,"rel":106},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowforge-nr-persistent-context\u002Fissues\u002F17",[26],"#17",[84,109,110,111],{},"Add a Last Seen status for devices connecting to FlowFuse. ",[22,112,115],{"href":113,"rel":114},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F1599",[26],"#1599",[84,117,118,119],{},"Added a check to ensure the team slug is unique. ",[22,120,123],{"href":121,"rel":122},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F1609",[26],"#1609",[84,125,126,127],{},"Optionally set snapshot as target at creation, to quickly roll out changes to remote deployments ",[22,128,131],{"href":129,"rel":130},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F1527",[26],"#1527",[84,133,134],{},"Agents are more rugged when starting up if they're unable to connect to FlowFuse, and will retry to connect.",[84,136,137,138,142],{},"With FlowFuse v1.4 some changes were made under the hood to speed up the recovery\nof Node-RED instances. On terminal failures of an instance it will now be\nautomatically be redeployed with the correct flows. This uses Kubernetes features\nand is also available if you've installed through ",[22,139,141],{"href":140},"\u002Fdocs\u002Finstall\u002Fkubernetes\u002F","kubernetes",".\nTo migrate the old style of deployments to this system a restart or stack upgrade is needed.",[30,144,146],{"id":145},"bug-fixes","Bug Fixes",[12,148,149],{},"We've fixed the following bugs in this release.",[81,151,152,160,166],{},[84,153,154,155],{},"Deleting your only team, doesn't exit from the team UI. ",[22,156,159],{"href":157,"rel":158},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F1630",[26],"#1630",[84,161,162,163],{},"Async Team Slug Check. ",[22,164,123],{"href":121,"rel":165},[26],[84,167,168,169],{},"Improve communication of Device Last Seen and Status ",[22,170,115],{"href":113,"rel":171},[26],[30,173,175],{"id":174},"contributors","Contributors",[12,177,178],{},"We'd like the thank the following for their contributions to this release:",[81,180,181],{},[84,182,183,188,189],{},[22,184,187],{"href":185,"rel":186},"https:\u002F\u002Fgithub.com\u002FUlisesGascon",[26],"UlisesGascon"," for their work on ",[22,190,193],{"href":191,"rel":192},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Finstaller\u002Fpull\u002F74",[26],"#74",[12,195,196,197,201],{},"As an open-source project, we welcome community involvement in what we're building.\nIf you're interested in contributing, checkout our ",[22,198,200],{"href":199},"\u002Fdocs\u002Fcontribute\u002F","guide in the docs",".",[30,203,205],{"id":204},"try-it-out","Try it out",[12,207,208,209,201],{},"We're confident you can have self managed FlowFuse running locally in under 30 minutes.\nYou can install FlowFuse yourself via a variety of install options. You can find out more details ",[22,210,212],{"href":211},"\u002Fdocs\u002Finstall\u002Fintroduction\u002F","here",[12,214,215,216,220],{},"If you'd rather use our hosted offering: ",[22,217,219],{"href":24,"rel":218},[26],"Get started for free"," on FlowFuse Cloud.",[30,222,224],{"id":223},"upgrading-flowfuse","Upgrading FlowFuse",[12,226,227,228,232],{},"[FlowFuse Cloud](",[229,230],"binding",{"value":231},"site.appURL",") is already running 1.4.",[12,234,235,236,201],{},"If you installed a previous version of FlowFuse and want to upgrade, our documentation provides a\nguide for ",[22,237,239],{"href":238},"\u002Fdocs\u002Fupgrade\u002F","upgrading your FlowFuse instance",[30,241,243],{"id":242},"getting-help","Getting help",[12,245,246,247,251],{},"Please check FlowFuse's ",[22,248,250],{"href":249},"\u002Fdocs\u002F","documentation"," as the answers to many questions are covered there.",[12,253,254,255,260],{},"If you hit any problems with the platform please raise an ",[22,256,259],{"href":257,"rel":258},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues",[26],"issue on GitHub",".\nThat's also a great place to send us any feedback or feature requests.",[12,262,263,264],{},"You can also get help on ",[22,265,268],{"href":266,"rel":267},"https:\u002F\u002Fdiscourse.nodered.org\u002F",[26],"the Node-RED forums",[12,270,271,272],{},"As well as in the ",[22,273,276],{"href":274,"rel":275},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fdiscussions",[26],"forum within our Github project",[12,278,279,280,284,285],{},"Chat with us on the ",[281,282,283],"code",{},"#flowfuse"," channel on the ",[22,286,289],{"href":287,"rel":288},"https:\u002F\u002Fnodered.org\u002Fslack",[26],"Node-RED Slack workspace",[12,291,292,293],{},"You can raise a support ticket by emailing ",[22,294,296],{"href":295},"mailto:support@flowfuse.com","support@flowfuse.com",[12,298,299],{},"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.",{"title":301,"searchDepth":302,"depth":302,"links":303},"",4,[304,306,307,308,309,310,311],{"id":32,"depth":305,"text":33},2,{"id":78,"depth":305,"text":79},{"id":145,"depth":305,"text":146},{"id":174,"depth":305,"text":175},{"id":204,"depth":305,"text":205},{"id":223,"depth":305,"text":224},{"id":242,"depth":305,"text":243},null,"2023-02-16","md","\u002Fblog\u002F2023\u002F02\u002Fimages\u002Fff-r14-image.png",{"excerpt":317},{"type":9,"value":318},[319],[12,320,14],{},true,"\u002Fblog\u002F2023\u002F02\u002Fflowforge-1-4-0-released",{"title":5,"description":14},{"loc":322},"blog\u002F2023\u002F02\u002Fflowforge-1-4-0-released","Our second release of 2023 with some great new features to try out.",[328,329,330],"posts","flowfuse","releases","vbg4zTmUYjQ","mCHQQja3_vZtHZDdOU7NoZ5bed5DN9av23W2jPV972s",[],1785960787399]