[{"data":1,"prerenderedAt":292},["ShallowReactive",2],{"blog-\u002Fblog\u002F2022\u002F11\u002Fflowforge-1-1-released":3},{"id":4,"title":5,"body":6,"description":12,"extension":281,"meta":282,"navigation":287,"path":288,"seo":289,"stem":290,"__hash__":291},"blog\u002Fblog\u002F2022\u002F11\u002Fflowforge-1-1-released.md","FlowFuse 1.1 released with persistent file storage",{"type":7,"value":8,"toc":268},"minimark",[9,13,16,21,31,38,42,50,53,56,60,69,72,143,147,150,163,171,176,194,208,212,220,227,231,239,248,261],[10,11,12],"p",{},"Persist files on your FlowFuse Projects, publish locally developed flows to dozens of Devices in a few clicks, and use our new interface for managing Project Deployments.",[10,14,15],{},"We're pleased to announce version 1.1 is now available! The latest release of the FlowFuse application contains new features, many improvements, and bug fixes. 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.",[17,18,20],"h2",{"id":19},"features","Features",[10,22,23,30],{},[24,25,29],"a",{"href":26,"rel":27},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F998",[28],"nofollow","Persistent File Storage"," We've had a great deal of feedback\nfrom our customers that being able to persist files in a project is a vital feature\nin Node-RED. In FlowFuse 1.1 flows can now create and persist files within\nyour Projects. We know those files are used in many creative ways and we're looking\nforward to seeing how users improve their Projects using this new feature.",[10,32,33,37],{},[24,34,36],{"href":35},"\u002Fdocs\u002Fmigration\u002Fnode-red-tools\u002F","Import Snapshots from Outside FlowFuse"," Developers may wish to\nwork on Node-RED in a local environment but want an easy path to share that with their team. You can now link your Node-RED instances running outside of FlowFuse and push Snapshots directly into your FlowFuse Projects to leverage FlowFuse fully.  With this new feature we've made it effortless to push a local build of a project to FlowFuse for deployment to your staging and production FlowFuse instances.",[17,39,41],{"id":40},"improvements","Improvements",[10,43,44,49],{},[24,45,48],{"href":46,"rel":47},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F1046",[28],"Project Deployments UX","\nWe've reworked the interface for managing your FlowFuse Deployments of Node-RED.\nWe are seeing FlowFuse users deploying their Projects to edge devices at scale.\nThis is another step towards making it easier for users to manage a large quantity\nof devices in their Projects.",[10,51,52],{},"When users change their username, email address, or password they'll now be\nnotified through email of changes to ensure they were made by the\nuser.",[10,54,55],{},"In this release a lot of effort went into the install process, specifically the\nlocal install method. First and foremost; a default Stack and Template will be\ninstalled automatically. That will ensure users get up and running with\nNode-RED more quickly. Administrators of each platform can still change Stacks\nand Templates when needed. Secondly, the installer now auto generates the\nconfiguration file for Mosquitto, the MQTT broker FlowFuse uses. This again should save\nadministrators time when installing FlowFuse.",[17,57,59],{"id":58},"bug-fixes","Bug Fixes",[10,61,62,63,68],{},"The v1.0.1 release included a bug fix where ",[24,64,67],{"href":65,"rel":66},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F1186",[28],"snapshot rollbacks","\ndidn't work, which has also been included in v1.1 onwards.",[10,70,71],{},"We've fixed the following bugs in this release.",[73,74,75,84,92,100,108,116,124,132,140],"ul",{},[76,77,78,79],"li",{},"When installing the stack during a FlowFuse installation the process would quit on Windows ",[24,80,83],{"href":81,"rel":82},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Finstaller\u002Fissues\u002F62",[28],"#62",[76,85,86,87],{},"After accepting an invite to join a team, users are no longer seeing a blank page ",[24,88,91],{"href":89,"rel":90},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F1208",[28],"#1208",[76,93,94,95],{},"Pagination on device deployments wasn't showing all devices ",[24,96,99],{"href":97,"rel":98},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F1207",[28],"#1207",[76,101,102,103],{},"Markdown rendering when selecting the project type wasn't quite working, fixed now! ",[24,104,107],{"href":105,"rel":106},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F1171",[28],"#1171",[76,109,110,111],{},"Continuous spinner in UI body when entering a new (short) password ",[24,112,115],{"href":113,"rel":114},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F1280",[28],"#1280",[76,117,118,119],{},"Friendly stack name not shown in the Change Project Stack option list ",[24,120,123],{"href":121,"rel":122},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F1169",[28],"#1169",[76,125,126,127],{},"The stacks view in the admin area didn't render properly ",[24,128,131],{"href":129,"rel":130},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F1260",[28],"#1260",[76,133,134,135],{},"Like the deployments page, pagination for stacks was broken. ",[24,136,139],{"href":137,"rel":138},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F1164",[28],"#1164",[76,141,142],{},"Several UX and UI bugs got polished away!",[17,144,146],{"id":145},"contributors","Contributors",[10,148,149],{},"We'd like the thank the following for their contributions to this release:",[10,151,152,157,158],{},[24,153,156],{"href":154,"rel":155},"https:\u002F\u002Fgithub.com\u002Fmikermcneil",[28],"mikermcneil"," for their work on ",[24,159,162],{"href":160,"rel":161},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fpull\u002F1301",[28],"#1301",[10,164,165,166,170],{},"As an open-source project, we welcome community involvement in what we're building.\nIf you're interested in contributing, checkout our ",[24,167,169],{"href":168},"\u002Fdocs\u002Fcontribute\u002F","guide in the docs",".",[172,173,175],"h3",{"id":174},"try-it-out","Try it out",[10,177,178,179,183,184,188,189,193],{},"As said before, a lot of effort went into the local installer. We're confident\nyou can have your own FlowFuse running locally in about 30 minutes.\n",[24,180,182],{"href":181},"\u002Fdocs\u002Fcontribute\u002Flocal\u002F","Get started right away!","\n(",[24,185,187],{"href":186},"\u002Fdocs\u002Finstall\u002Fdocker\u002F","Docker"," and ",[24,190,192],{"href":191},"\u002Fdocs\u002Finstall\u002Fkubernetes\u002F","Kubernetes","\nare available too!)",[10,195,196,197,202,203,207],{},"If you'd rather use our hosted offering: ",[24,198,201],{"href":199,"rel":200},"https:\u002F\u002Fapp.flowfuse.com\u002Faccount\u002Fcreate?code=RELEASE11",[28],"Sign up for FlowFuse Cloud","\nwith the coupon ",[204,205,206],"strong",{},"RELEASE11"," to get your first project free for a month.",[172,209,211],{"id":210},"upgrading-flowfuse","Upgrading FlowFuse",[10,213,214,219],{},[24,215,218],{"href":216,"rel":217},"https:\u002F\u002Fapp.flowfuse.com",[28],"FlowFuse Cloud"," is already running 1.1. To use\npersisted files you'll need to upgrade your projects stack. You'll be prompted\nto do so on the project page.",[10,221,222,223],{},"If you installed a previous version of FlowFuse and want to upgrade, our documentation provides a\nguide for ",[24,224,226],{"href":225},"\u002Fdocs\u002Fupgrade\u002F","upgrading your FlowFuse instance",[172,228,230],{"id":229},"getting-help","Getting help",[10,232,233,234,238],{},"Please check FlowFuse's ",[24,235,237],{"href":236},"\u002Fdocs\u002F","documentation"," as the answers to many questions are covered there.",[10,240,241,242,247],{},"If you hit any problems with the platform please raise an ",[24,243,246],{"href":244,"rel":245},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues",[28],"issue on GitHub",".\nThat also includes if you have any feedback or feature requests.",[10,249,250,251,255,256,170],{},"Chat with us on the ",[252,253,254],"code",{},"#flowfuse"," channel on the ",[24,257,260],{"href":258,"rel":259},"https:\u002F\u002Fnodered.org\u002Fslack",[28],"Node-RED Slack workspace",[10,262,263,264],{},"You can also raise a support ticket by emailing ",[24,265,267],{"href":266},"mailto:support@flowfuse.com","support@flowfuse.com",{"title":269,"searchDepth":270,"depth":270,"links":271},"",2,[272,273,274,275],{"id":19,"depth":270,"text":20},{"id":40,"depth":270,"text":41},{"id":58,"depth":270,"text":59},{"id":145,"depth":270,"text":146,"children":276},[277,279,280],{"id":174,"depth":278,"text":175},3,{"id":210,"depth":278,"text":211},{"id":229,"depth":278,"text":230},"md",{"navTitle":5,"excerpt":283},{"type":7,"value":284},[285],[10,286,12],{},true,"\u002Fblog\u002F2022\u002F11\u002Fflowforge-1-1-released",{"title":5,"description":12},"blog\u002F2022\u002F11\u002Fflowforge-1-1-released","Q3yg21sCY_K7Mh_wHMKYl1EcI3SV4MiOEDwNnQmgEbY",1780132425002]