Valkey Support

As long as Valkey remains API compatible with original Redis, there's no reason why you shouldn't be able to use it.

Automatically closed - issue fixed for 2 weeks with no activity.

Thank you @Berdir :)

The Ubertus team, including myself, are also interested in support for Valkey.

For those not familiar with https://valkey.io it is a successor to Redis. Details at https://en.wikipedia.org/wiki/Valkey

The challenge with the latest Redis is that they modified its license from BSD-3-Clause to RSALv2 and SSPLv1 on March 20th, 2024. "This prompted a large portion of the user and developer community, including contributors from Alibaba Group, Amazon, Ericsson, Google, Huawei and Tencent, to fork the code of Redis 7.2.4 as a project of the Linux Foundation under the new name Valkey, retaining the BSD license.[3] Valkey 8.0, released six months after the fork, featured improved threading and significantly improved performance."

A couple of comments, though:

• Redis ⪚ 8.0 is available under the open source AGPLv3 license too, not just the non-open ones
• The toxigon.com link attempts to install suspicious extensions to the browser: either they are compromized, or doing it willingly. So beware that link. Disabling JS allows one to see the page.

> Redis ≥ 8.0 is available under the open source AGPLv3 license too, not just the non-open ones

The problem is that hosting platforms such as platform.sh and also general cloud platforms like AWS and so on can no longer provide redis as a service.

That said, I don't really get what #5 is trying to say. valkey is compatible with phpredis and so on, there is no indication that this module wouldn't be compatible with valkey out of the box. If you see any indication that this isn't the case, then open a bug report with specifics and extend our gitlab CI test coverage to test against valkey. Otherwise, just test it and switch.

https://github.com/ddev/ddev-redis/issues/28