[{"data":1,"prerenderedAt":194},["ShallowReactive",2],{"blog-\u002Fblog\u002F2022\u002F05\u002Fflowforge-05-released":3},{"id":4,"title":5,"body":6,"description":12,"extension":183,"meta":184,"navigation":189,"path":190,"seo":191,"stem":192,"__hash__":193},"blog\u002Fblog\u002F2022\u002F05\u002Fflowforge-05-released.md","FlowFuse 0.5 released",{"type":7,"value":8,"toc":174},"minimark",[9,13,16,19,26,39,44,47,50,53,61,64,87,91,94,103,107,110,113,116,119,122,125,134,138,146,150,158,161],[10,11,12],"p",{},"The cycle continues with our next regularly scheduled release, bringing a fresh\nnew look to the platform.",[10,14,15],{},"Since joining the team, Joe has been hard at work bringing a more consistent\ndesign language to what we're doing. This release brings a lot of his hardwork\nto the platform itself.",[10,17,18],{},"There's more to be done on the individual pages of the platform, but this\ngives us a solid framework to build on.",[10,20,21],{},[22,23],"img",{"alt":24,"src":25},"","\u002Fblog\u002F2022\u002F05\u002Fimages\u002Fff-05-dashboard.png",[27,28,29],"ul",{},[30,31,32],"li",{},[33,34,38],"a",{"href":35,"rel":36},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F430",[37],"nofollow","Epic #430 - Rebrand Forage App",[40,41,43],"h3",{"id":42},"copying-projects","Copying Projects",[10,45,46],{},"One of the usage scenarios we want to support is having an easy way to have separate\ntest and production environments. The previous release added the ability to configure\nenvironment variables on individual projects.",[10,48,49],{},"This release unlocks the next piece of the puzzle - making it easy to copy flows\nbetween projects.",[10,51,52],{},"The Project settings page has two new options:",[27,54,55,58],{},[30,56,57],{},"Copy Project lets you create a complete copy of the project.",[30,59,60],{},"Export to existing project lets you copy over selected aspects of the project\nover to another project.",[10,62,63],{},"In both cases, you get to pick what parts of the project should be copied.",[27,65,66,73,80],{},[30,67,68],{},[33,69,72],{"href":70,"rel":71},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F268",[37],"Epic #268 - Export Project",[30,74,75],{},[33,76,79],{"href":77,"rel":78},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F271",[37],"Story #271 - Duplicate Project",[30,81,82],{},[33,83,86],{"href":84,"rel":85},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F272",[37],"Story #272 - Export to Existing Project",[40,88,90],{"id":89},"improve-billing-information","Improve Billing Information",[10,92,93],{},"We've been getting some great feedback from the users of FlowFuse Cloud. One of the\nareas we identified as needing some more clarity was around the point users are\nasked to setup their billing information.",[27,95,96],{},[30,97,98],{},[33,99,102],{"href":100,"rel":101},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F563",[37],"Story #563 - Improve Information on billing",[40,104,106],{"id":105},"edge-devices","Edge Devices",[10,108,109],{},"Whilst we always want to deliver new functionality to end users in each release,\nsometimes bits of work don't fit naturally into a single four week iteration.",[10,111,112],{},"That's the case here with some of the preliminary work we've done to introduce\nthe idea of Edge Devices to the platform.",[10,114,115],{},"The goal here is to provide a way to easily deploy and manage Node-RED projects\non remote devices.",[10,117,118],{},"This release introduces a bunch of work to the core app and front-end to begin\nintroducing the concept of a Device. It includes the basic workflows for registering\na device on the platform and being able to assign it to a team.",[10,120,121],{},"The whole feature is hidden behind a feature flag so users on FlowFuse Cloud won't\nsee any of this quite yet.",[10,123,124],{},"The next release will introduce the Edge Agent piece of this - the bit that runs\non devices.",[27,126,127],{},[30,128,129],{},[33,130,133],{"href":131,"rel":132},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F446",[37],"Epic #446 - Devices",[40,135,137],{"id":136},"upgrading-flowfuse","Upgrading FlowFuse",[10,139,140,141,145],{},"If you installed a previous version of FlowFuse  and want to upgrade, our documentation provides a\nguide for ",[33,142,144],{"href":143},"\u002Fdocs\u002Fupgrade\u002F#upgrading-flowfuse","upgrading FlowFuse on a local server",".",[40,147,149],{"id":148},"getting-help","Getting help",[10,151,152,153,145],{},"If you hit any problems with the platform, or have questions to ask, please do\nraise an ",[33,154,157],{"href":155,"rel":156},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues",[37],"issue on GitHub",[10,159,160],{},"That also includes if you have any feedback or feature requests.",[10,162,163,164,168,169,145],{},"We also have a ",[165,166,167],"code",{},"#flowfuse"," channel on the ",[33,170,173],{"href":171,"rel":172},"https:\u002F\u002Fnodered.org\u002Fslack",[37],"Node-RED Slack workspace",{"title":24,"searchDepth":175,"depth":175,"links":176},2,[177,179,180,181,182],{"id":42,"depth":178,"text":43},3,{"id":89,"depth":178,"text":90},{"id":105,"depth":178,"text":106},{"id":136,"depth":178,"text":137},{"id":148,"depth":178,"text":149},"md",{"navTitle":5,"excerpt":185},{"type":7,"value":186},[187],[10,188,12],{},true,"\u002Fblog\u002F2022\u002F05\u002Fflowforge-05-released",{"title":5,"description":12},"blog\u002F2022\u002F05\u002Fflowforge-05-released","gnYEqTM_6IMDgdhbR5at6OYM75fRjBEk9yx2py8a0DM",1780132424773]