Just switched my #SelfHosted#PeerTube instance from using #Redis to #Valkey now that it has a stable release out as a #Docker#container too, and.. that went too easily 😅. I know this makes sense as it is 100% compatible, but it still feels quite amazing to have it just work.
In case it helps; I just switched to using the valkey/valkey:7-alpine image, and because I also renamed things in my docker-compose I added PEERTUBE_REDIS_HOSTNAME=valkey to the PeerTube .env file too. That's it!
@purelinux We have moved some services to Redict. If you want stability and don't care about specific new features, it's a reliable choice that doesn't need much attention. It's just running nicely just as Redis once did.
If Redis was a core part of your application and you benefit a lot of community and new features, you might come to another conclusion, though.
@mistersql surely if it's protocol compatible, then they would have to break both redis-py and their own redis clients to pull-off breaking though? Gotta be done slowly, like MySQL 8 and MariaDB
⚠️ @forrestbrazeal on the inside threat to OSS
🍴Vicki Boykis says Redis is forked
👻 @johnonolan says Ghost is federating
🦙 Meta Engineering announces Llama 3
❓ @eieio's questions to ask when you don't want to work
🎙 hosted by @jerod
"A new project to resume development on the formerly open-source Redis project. We're calling it #Valkey, since it's a twist on the key-value datastore."