# Make redis config node more "dynamic"

**URL:** <https://discourse.nodered.org/t/make-redis-config-node-more-dynamic/77814>\
**Category:** General\
**Tags:** docker\
**Created:** [22 April 2023 10:58 UTC](https://discourse.nodered.org/t/make-redis-config-node-more-dynamic/77814 "2023-04-22T10:58:12Z")\
**Posts on this page:** 1\
**Showing post:** 1

<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:** [22 April 2023 10:58 UTC](https://discourse.nodered.org/t/make-redis-config-node-more-dynamic/77814/1 "2023-04-22T10:58:12Z")

</div>

In this project [GitHub - golfvert/WIS2-GlobalBroker-NodeRed: Basic reference of a Global Broker for WIS2](https://github.com/golfvert/WIS2-GlobalBroker-NodeRed) available as a ready to use container, I am making use of [https://flows.nodered.org/node/node-red-contrib-redis](https://flows.nodered.org/node/node-red-contrib-redis) .  
This contrib node works great.  
At the moment, I am using redis in a non-cluster mode. And as part of the setup, a redis instance must be on the same docker bridged network.  
I'd like to change that and be able to use an existing redis service that could be in cluster to improve reliability.  
However, the current node doesn't permit the configuration of the cluster mode dynamically (eg. through an ENV variable or using dynamic msg input). Typically, what is possible with the excellent MQTT nodes.

I wonder what are the options here.

1. asking the maintainer to add this feature ? I've done that, maybe that will happen...  
If not, some ideas on Plan B:
2. forking the repo and add this feature myself. Is there some simple example how I could use to do that. Typically, another contrib node having this feature that I could "borrow"...
3. having two config nodes one with cluster and one without and be able to switch dynamically at startup ? Not sure if that is doable as the flows.json is part of the container and is not stored on a permanent volume.

Some other ideas ?  
Thanks for your clues 🙂

---

_[View the full topic](https://discourse.nodered.org/t/make-redis-config-node-more-dynamic/77814)._
