You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the go-redis client there is a universal client that allows you setup either a normal/cluster/sentinel client depending on the config you give. See https://redis.uptrace.dev/guide/universal.html
Would you be open to accepting a PR for a universal redis client in deadpool-redis?
This would prevent code duplication in users of deadpool-redis and would allow them to easily switch between normal/cluster/sentinel clients
The text was updated successfully, but these errors were encountered:
Sure thing. I always wondered why there needed to be three distinct pools for that. I only use a single redis instance so I've never actually bothered with redis cluster/sentinel. It is purely driven by PRs from the community.
Currently chirpstack has it own thin wrapper around deadpool-redis (https://github.com/chirpstack/chirpstack/blob/master/chirpstack/src/storage/mod.rs)
In the go-redis client there is a universal client that allows you setup either a normal/cluster/sentinel client depending on the config you give. See https://redis.uptrace.dev/guide/universal.html
Would you be open to accepting a PR for a universal redis client in deadpool-redis?
This would prevent code duplication in users of deadpool-redis and would allow them to easily switch between normal/cluster/sentinel clients
The text was updated successfully, but these errors were encountered: