# Shared Node-RED Project Across Multiple RPi's

**URL:** https://discourse.nodered.org/t/shared-node-red-project-across-multiple-rpis/24765
**Category:** General
**Created:** [13 April 2020 15:09 UTC](https://discourse.nodered.org/t/shared-node-red-project-across-multiple-rpis/24765 "2020-04-13T15:09:57Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![dudleyjosh](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dudleyjosh/32/105799_2.png) [@dudleyjosh](https://discourse.nodered.org/u/dudleyjosh)
#### Post date: [13 April 2020 15:09 UTC](https://discourse.nodered.org/t/shared-node-red-project-across-multiple-rpis/24765/1 "2020-04-13T15:09:57Z")

</div>

I'm not super savvy with Git & GitHub yet (learning, slowly but surely) and I've been playing with Node-RED projects for the past few days learning how to get projects setup and linked to a GitHub repository from my various Pi's.

I'm looking for help to understand how to best transition several Pi's that are already currently running Node-RED with the same flows in a production environment and get them all setup equivalently using Node-RED projects, all linked to the same GitHub repository? One of them is already setup using Node-RED projects and linked to a GitHub repository.

I am wanting to get to a place where if tweaks and changes are made on any one of the Pi's it will be easy to push/pull code to/from GitHub to keep them all in sync.

---

<div class="post-metadata">

### Author: ![nlecaude](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/nlecaude/32/25_2.png) [@nlecaude](https://discourse.nodered.org/u/nlecaude)
#### Post date: [13 April 2020 17:55 UTC](https://discourse.nodered.org/t/shared-node-red-project-across-multiple-rpis/24765/2 "2020-04-13T17:55:02Z")

</div>

Depending on the number of devices you need to manage I suggest you check Balena: [https://www.balena.io](https://www.balena.io)  
It pretty much solves the issue of "Push once. update many"

---

<div class="post-metadata">

### Author: ![dudleyjosh](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dudleyjosh/32/105799_2.png) [@dudleyjosh](https://discourse.nodered.org/u/dudleyjosh)
#### Post date: [13 April 2020 20:34 UTC](https://discourse.nodered.org/t/shared-node-red-project-across-multiple-rpis/24765/3 "2020-04-13T20:34:40Z")

</div>

Thanks for the info. Balena certainly looks like it would do the trick but it is also more than I need or want. I'm only managing a handful of devices specific to an in-house manufacturing process... so I'm trying to keep it simple without adding other various services.

---

<div class="post-metadata">

### Author: ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [14 April 2020 07:33 UTC](https://discourse.nodered.org/t/shared-node-red-project-across-multiple-rpis/24765/4 "2020-04-14T07:33:53Z")

</div>

Ansible would be another possibility, you could not only use it for updating the flows across the network but also for setting up the Pis in the first place.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)
#### Post date: [13 June 2020 07:33 UTC](https://discourse.nodered.org/t/shared-node-red-project-across-multiple-rpis/24765/5 "2020-06-13T07:33:54Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
