# Standard flows that could be overwritten with project specific changes
**URL:** https://discourse.nodered.org/t/standard-flows-that-could-be-overwritten-with-project-specific-changes/44434
**Category:** General
**Created:** [20 April 2021 05:49 UTC](https://discourse.nodered.org/t/standard-flows-that-could-be-overwritten-with-project-specific-changes/44434 "2021-04-20T05:49:10Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@eastling](https://discourse.nodered.org/u/eastling)
#### Post date: [20 April 2021 05:49 UTC](https://discourse.nodered.org/t/standard-flows-that-could-be-overwritten-with-project-specific-changes/44434/1 "2021-04-20T05:49:10Z")
Hi guys,
We are developing a set of flows that are meant to be re-used on several deployments (lets call this our "standard" code).
However each deployment could have its own little tweak (lets call this part the "custom" code). It would be preferably to have the "standard" code in one repository and only the "custom" parts in a deployment specific repository.
I am exploring which ways there are to handle this. One way could maybe be to use "node-red-contrib-flow-manager" and put the custom code in subflows which then would be stored in the "custom" repository.
I wanted to hear if someone else have any thoughts or experience doing something similar and what might your approach to this be?
Many thanks in advance,
Martin
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [19 June 2021 05:49 UTC](https://discourse.nodered.org/t/standard-flows-that-could-be-overwritten-with-project-specific-changes/44434/2 "2021-06-19T05:49:31Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.