Rename redis to valkey in readme

[tlhunter]

Certainly the code samples should all say valkey. Other things I'm not so sure about. I'll need to go over the Valkey website docs and command references and whatnot to update URLs.

Lots of open questions before this can land:

• Does Valkey use the redis:// protocol identifier? Is there a valkey://?
• Are all the config properties renamed from redis* to valkey*?

Also, how was this repo forked? Was it from a historical commit before a license change? I suppose Redis inc took over the redis module but ioredis wasn't affected, however as Redis introduced proprietary features I'm guessing ioredis added support and we wanted to revert it?

[mcollina]

lgtm

[mcollina]

Ops, I took a look and I fat fingered those changes, which I should have done earlier.

• Does Valkey use the redis:// protocol identifier? Is there a valkey://?

I think it should, but better check on the main repo.

• Are all the config properties renamed from redis* to valkey*?

I don't think so. We should keep supporting both for migration sake. The goal was a easy migration.

Also, how was this repo forked? Was it from a historical commit before a license change? I suppose Redis inc took over the redis module but ioredis wasn't affected, however as Redis introduced proprietary features I'm guessing ioredis added support and we wanted to revert it?

The main reason this was forked was because ioredis has been in a slow maintenance mode for a long time as Redis Inc put their effort in the module named redis, adding a lot of proprietary feature there, and even cloning/copying the best from ioredis.

A long time ago, @ShogunPanda and myself created a technique called autopipelining and added it to ioredis. Therefore, we know our way around this codebase. Therefore we had the knowledge to maintain this long-term.

Last but not least, I expected the clamp down on all Redis-related things we now see with all the independent clients. I expect all of them to become incompatible with Valkey long term.

At Platformatic, we needed an OSS version for our product, too.