[{"data":1,"prerenderedAt":148},["ShallowReactive",2],{"blog-\u002Fblog\u002F2023\u002F09\u002Frebranding-our-components":3},{"id":4,"title":5,"body":6,"description":12,"extension":137,"meta":138,"navigation":143,"path":144,"seo":145,"stem":146,"__hash__":147},"blog\u002Fblog\u002F2023\u002F09\u002Frebranding-our-components.md","Updating our branding across GitHub, npm and Dockerhub",{"type":7,"value":8,"toc":128},"minimark",[9,13,22,30,33,36,39,44,47,62,65,69,76,83,90,93,97,103,106,110,117],[10,11,12],"p",{},"Following our rename to FlowFuse last month, we are about to take the next\nset of steps to complete the rebrand. This time, focussed on the technical\nassets we produce.",[10,14,15,16,21],{},"Rebranding a company isn't a small undertaking, especially when your company\nname is also your product name. When we announced our ",[17,18,20],"a",{"href":19},"\u002Fblog\u002F2023\u002F08\u002Fflowforge-is-now-flowfuse\u002F","new name last month"," we\nprioritised updating the website, our documentation and social media presences.\nAll of the most visible things relating to the company name.",[10,23,24,25,29],{},"But we knew that wasn't the whole job done. The name ",[26,27,28],"code",{},"flowforge"," still appears\nin the technical resources we use and the artefacts we publish. Changing them\nis not as simple a task as changing some words on a website, so it has taken a bit\nmore time to get our plans in place for this next step.",[10,31,32],{},"I wanted to highlight the set of changes we'll be making in the coming days to\ncomplete this migration. For the vast majority of users, expecially those using\nFlowFuse Cloud, these changes will be completely transparent.",[10,34,35],{},"However, if you are contributing to any of our open source components, or consuming\nour npm or Docker packages directly, then please read on.",[10,37,38],{},"There are four areas we need to migrate.",[40,41,43],"h3",{"id":42},"github-organization","GitHub Organization",[10,45,46],{},"As a company everything we do revolves around our GitHub Organization. Our\nsource code, release planning, this website, and far more all live there.",[10,48,49,50,53,54,57,58,61],{},"Step one of our migration will be renaming the organization to ",[26,51,52],{},"FlowFuse",", so instead\nof ",[26,55,56],{},"https:\u002F\u002Fgithub.com\u002Fflowforge"," we will now live at ",[26,59,60],{},"https:\u002F\u002Fgithub.com\u002FFlowFuse",".",[10,63,64],{},"Renaming organizations on GitHub, whilst not something done lightly, is well catered\nfor. Many existing urls should get automatically redirected - so any existing\nlinks will still work. We will, of course, do the work to update any urls in our docs.",[40,66,68],{"id":67},"npm-package-names","NPM package names",[10,70,71,72,75],{},"We publish a number of packages to the public Node.js Package Manager (npm) repository\nunder the ",[26,73,74],{},"@flowforge"," name.",[10,77,78,79,82],{},"After this week's release is done, we'll be updating all of our packages to publish\nunder the ",[26,80,81],{},"@flowfuse"," name and no longer updating the packages under the old name.",[10,84,85,86,89],{},"This will impact anyone who has installed any of our components directly from ",[26,87,88],{},"npm",". For\nexample, the Device Agent or Node-RED Dashboard 2.0.",[10,91,92],{},"We will provide specific upgrade instructions for each of the affected components once\nthe move is done.",[40,94,96],{"id":95},"docker-images","Docker Images",[10,98,99,100,102],{},"We publish container images to Dockerhub under the ",[26,101,28],{}," name. Once\nwe've updated our npm package names, we'll also be updating our container tags\nto use the new name.",[10,104,105],{},"If you are using our helm or Docker Compose projects, we'll have a new release that\nwill help get you moved over to the new image names. Likewise our Digital Ocean\nand AWS Marketplace offerings will be updated - and instructions provided for existing\nusers to migrate over.",[40,107,109],{"id":108},"flowfuse-cloud","FlowFuse Cloud",[10,111,112,113,116],{},"The final step we have to make is to move FlowFuse Cloud over to its new home\nat ",[26,114,115],{},"app.flowfuse.com",". We have to co-ordinate the update with all of our customers\nwho use SSO to login to ensure they can continue to access the platform.",[10,118,119,120,123,124,127],{},"Once that is done, it will be a seamless transition for everyone. Existing Node-RED\ninstances will continue to use the ",[26,121,122],{},"*.flowforge.cloud"," domain, but then all new\ninstances will use the ",[26,125,126],{},"*.flowfuse.cloud"," domain.",{"title":129,"searchDepth":130,"depth":130,"links":131},"",2,[132,134,135,136],{"id":42,"depth":133,"text":43},3,{"id":67,"depth":133,"text":68},{"id":95,"depth":133,"text":96},{"id":108,"depth":133,"text":109},"md",{"navTitle":5,"excerpt":139},{"type":7,"value":140},[141],[10,142,12],{},true,"\u002Fblog\u002F2023\u002F09\u002Frebranding-our-components",{"title":5,"description":12},"blog\u002F2023\u002F09\u002Frebranding-our-components","52uPGam1mN0kuuyJKNf2We4b4KS4CLBQIcTSmCmXMqM",1780070550928]