Redis replacement - valkey - missing systemd service

[Gorian]

Info

version: 42680

Description

Redis, and the bundle redis-native has been replaced in recent versions by valkey, which seems to be a drop-in FOSS replacement. However, the replacement isn't documented, and it doesn't come with a systemd service. This leads to broken servers when an updates removes Redis and there's no longer any redis service running. Ideally, we'd adapt a systemd service file, E.G. https://github.com/valkey-io/valkey/blob/unstable/utils/systemd-valkey_server.service and then possibly alias is to the redis-service that was previously ran by the redis bundle for backwards compatability.

[bryteise]

I'm not sure I want to just have this default enable if redis was enabled as there are what looks to be some differences between config in what we were last shipping of redis and the current valkey stuff. I did make the main service use a default valkey.conf that is now shipped. That conf will try and load an /etc/redis.conf if it exists (and an /etc/valkey.conf if it exists too) and will use the /var/lib/redis directory for its state still (as well as the redis user and group).

[Gorian]

Unfortunately, I don't know anything about valkey - I never heard of it before digging into the reason my server stopped working, as it was dependent on Redis. I do know that since valkey was auto-installed with the OS updated, all I had to do to make it work was copy the systemd service file, update the binary path, and then start (and enable it) and with no additional configuration (since I was using the default redis config on the default port), it just worked. I can see how it might be complicated if you had a more in-depth configuration though.