# Off topic - kinda - LOCAL way for better handling of rolling out updates to flows
**URL:** https://discourse.nodered.org/t/off-topic-kinda-local-way-for-better-handling-of-rolling-out-updates-to-flows/97508
**Category:** General
**Created:** [9 June 2025 11:40 UTC](https://discourse.nodered.org/t/off-topic-kinda-local-way-for-better-handling-of-rolling-out-updates-to-flows/97508 "2025-06-09T11:40:47Z")
**Posts on this page:** 13
**Page:** 1
### Author:  [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [9 June 2025 11:40 UTC](https://discourse.nodered.org/t/off-topic-kinda-local-way-for-better-handling-of-rolling-out-updates-to-flows/97508/1 "2025-06-09T11:40:47Z")
I've no idea how this works, and am taking a guess that `github` is the _IDEAL_ thing to use for version management.
I am going through a horrible piece of the learning curve and seeing the problems with how I made code.
I write code in function blocks with the mechanics and _eye candy_ all together.
Recent events have shown me the increasing problem doing things this way.
If I have 3 (probably 6) machines that all need a "base line" my way is not nice.
I need to write it with the structure of two parts:
the _mechanics_ and the _eye candy_ as two separate parts.
Not in _function blocks_ as I have been.
So anyway, from the early days, I would have to sit down for HOURS rolling out updates to all instances on the same machine - let alone machines.
Subflows did make life a LOT EASIER.
But there is a problem with them too..... Version tracking.
For now I make myself add the date to the description when I'm editing the node/subflow.
Then I look for the latest dated one and propagate it to the other machines.
But I not familiar with any ..... _options_ to do that.
I'd prefer to keep things _in house_ and not via github.
(Nothing against it/them. For now I'd like to keep control of where things are.)
So if I want to get busy tidying up subflows, I can do a _MASTER_ one; save it, then it gets _sent out_ to all devices using it.
I know that is nothing like how things really work. But for simplicity.....
Are there any programs/systems that allow this? Locally on the local network?
Thanks in advance.
---
### Author:  [@GogoVega](https://discourse.nodered.org/u/GogoVega)
#### Post date: [9 June 2025 11:44 UTC](https://discourse.nodered.org/t/off-topic-kinda-local-way-for-better-handling-of-rolling-out-updates-to-flows/97508/2 "2025-06-09T11:44:54Z")
Did you know that FlowFuse exists? There are of course other solutions, but FF allows you to easily manage multiple NR instances in addition to creating versioning.
---
### Author:  [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [9 June 2025 11:46 UTC](https://discourse.nodered.org/t/off-topic-kinda-local-way-for-better-handling-of-rolling-out-updates-to-flows/97508/3 "2025-06-09T11:46:52Z")
Ok, indulge me....
What's `fuse flow`?
See!
`FlowFuse` Ooops.
I'll search for it, but local help is kind appreciated.
😉
---
### Author:  [@GogoVega](https://discourse.nodered.org/u/GogoVega)
#### Post date: [9 June 2025 11:49 UTC](https://discourse.nodered.org/t/off-topic-kinda-local-way-for-better-handling-of-rolling-out-updates-to-flows/97508/4 "2025-06-09T11:49:51Z")
Nick's company where Joe, Steve, Ben and more work.
> **[FlowFuse • Build workflows and integrations that optimize your industrial...](https://flowfuse.com)**
>
> Quickly build workflows, applications and integrations that optimize your operations with our low-code, open-source, end to end platform.
---
### Author:  [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [9 June 2025 11:52 UTC](https://discourse.nodered.org/t/off-topic-kinda-local-way-for-better-handling-of-rolling-out-updates-to-flows/97508/5 "2025-06-09T11:52:14Z")
But that's off site isn't it?
I'd prefer to keep things on site.
(And although there is a free limited time demo)
I don't think I would get enough of an understanding of it's workings in that time.
---
### Author:  [@GogoVega](https://discourse.nodered.org/u/GogoVega)
#### Post date: [9 June 2025 11:52 UTC](https://discourse.nodered.org/t/off-topic-kinda-local-way-for-better-handling-of-rolling-out-updates-to-flows/97508/6 "2025-06-09T11:52:57Z")
There are Cloud vs Self-Hosted
---
### Author:  [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [9 June 2025 12:00 UTC](https://discourse.nodered.org/t/off-topic-kinda-local-way-for-better-handling-of-rolling-out-updates-to-flows/97508/7 "2025-06-09T12:00:04Z")
I'm not sure, but I am don't seem to get my head around how it _works_.
That is: How it .... _connects_..... Nah.
Vocab() is rebooting. 😢
It is "conceptual only" to me at this stage.
I have never really dealt with this sort of thing ever in my life.
I get the _bigger picture_ of it, but not in a practical way - if you know what I mean.
(Which I'm guessing you don't. No offence)
So I am not understanding how I would use it.
I don't really have anyone to talk to about it either.
So it is somewhat confusing for me.
---
### Author:  [@GogoVega](https://discourse.nodered.org/u/GogoVega)
#### Post date: [9 June 2025 12:13 UTC](https://discourse.nodered.org/t/off-topic-kinda-local-way-for-better-handling-of-rolling-out-updates-to-flows/97508/8 "2025-06-09T12:13:28Z")
To install, follow the steps in the readme, and then you'll have all the FF documentation to use the interface.
PS: I'm not really using FF for this yet - it's my summer project 😋
> **[GitHub - FlowFuse/installer: A set of install scripts for FlowFuse](https://github.com/FlowFuse/installer)**
>
> A set of install scripts for FlowFuse
---
### Author:  [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [9 June 2025 12:14 UTC](https://discourse.nodered.org/t/off-topic-kinda-local-way-for-better-handling-of-rolling-out-updates-to-flows/97508/9 "2025-06-09T12:14:50Z")
Thanks.
I'll look at it when my head is a bit clearer.
(You have an appreciation of what I've just been through.)
---
### Author:  [@GogoVega](https://discourse.nodered.org/u/GogoVega)
#### Post date: [9 June 2025 12:24 UTC](https://discourse.nodered.org/t/off-topic-kinda-local-way-for-better-handling-of-rolling-out-updates-to-flows/97508/10 "2025-06-09T12:24:59Z")
😂 I also have a bit of a headache 🤣
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [9 June 2025 13:33 UTC](https://discourse.nodered.org/t/off-topic-kinda-local-way-for-better-handling-of-rolling-out-updates-to-flows/97508/11 "2025-06-09T13:33:32Z")
Something else to consider.
Have you thought about having _another instance of Node-RED_ that runs your common flows? Effectively, that instance would be like an API server. You can use MQTT, HTTP (REST API), websockets or one of several other means of intercommunication.
---
### Author:  [@Sean-McG](https://discourse.nodered.org/u/Sean-McG)
#### Post date: [9 June 2025 15:08 UTC](https://discourse.nodered.org/t/off-topic-kinda-local-way-for-better-handling-of-rolling-out-updates-to-flows/97508/12 "2025-06-09T15:08:03Z")
TBH I would probably take a look at your whole setup, you recently posted about how you are using various Rpi servers, which made me think you could probably just use 1 for everything, which would make managing things a lot easier 😉
---
### Author:  [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [9 June 2025 20:54 UTC](https://discourse.nodered.org/t/off-topic-kinda-local-way-for-better-handling-of-rolling-out-updates-to-flows/97508/13 "2025-06-09T20:54:10Z")
Julian,
I still haven't got around to getting a second NR running on THIS machine. (My main computer/NUC)
So with that idea, I could make/update subflows and the like and then have it _roll out_ any new ones to the remote machines....
Hmmm..... interesting.
Steve,
As a base line there are 3 ras pies always on.
Yes, that is sort of an _artefact_ from when I first started and it was a version 1 RasPi.
I couldn't put too much load on it.
As time went on I added the second and WAY down the track added the third.
So why don't I put them all on one machine - say a RasPi 4 or 5?
Well, couple of things:
RasPi 4/5 are not exactly cheap.
But more so.....
Points of failure.
This way if one dies the others _pull the weight._
Not that they take over, but there are machines left that can tell me there is a problem.
If I have all 3 on one machine and it fails..... There's not way of knowing until things really don't work.
Maybe not really needed, but it is something in which I am interested and am learning (especially recently) the benefits and (what's the opposite of benefit?) of this method.