# RedBack - Node-Red as Backend

**URL:** <https://discourse.nodered.org/t/redback-node-red-as-backend/74481>\
**Category:** Share Your Projects\
**Created:** [31 January 2023 11:36 UTC](https://discourse.nodered.org/t/redback-node-red-as-backend/74481 "2023-01-31T11:36:30Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![greengolfer](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/greengolfer/32/28276_2.png) [@greengolfer](https://discourse.nodered.org/u/greengolfer)\
**Post date:** [4 February 2023 22:30 UTC](https://discourse.nodered.org/t/redback-node-red-as-backend/74481/14 "2023-02-04T22:30:21Z")

</div>

Not sure it matches exactly your request...

However, if you look at this [Use of NodeRed for international weather, climate, ocean, hydrology data exchange](https://discourse.nodered.org/t/use-of-nodered-for-international-weather-climate-ocean-hydrology-data-exchange/73104) and that [GitHub - golfvert/WIS2-GlobalBroker-NodeRed: Basic reference of a Global Broker for WIS2](https://github.com/golfvert/WIS2-GlobalBroker-NodeRed) it is kinda close.

The github repository is managed throughout the "project" feature of NodeRed. Then, when changes are made, a new docker image is made with the updated set of flows.

So, upgrading the flows is made by an upgrade of the docker container version.

The parameters (env variables) used within the various nodes are initialised using docker compose.

All this is currently deployed on an on-premise openstack cluster. Using ansible you can easily update all the docker-compose and then, done.

Fairly close to your 2., 3. and 4. I think.

---

_[View the full topic](https://discourse.nodered.org/t/redback-node-red-as-backend/74481)._