Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please cover Valkey alternatively to Redis (or support at least systemd.unit Alias=… properly) #22

Open
robert-scheck opened this issue May 18, 2024 · 0 comments

Comments

@robert-scheck
Copy link
Contributor

If you setup grommunio using Valkey instead of Redis, because Fedora plans to switch to it (which RHEL 10 will most likely inherit), it would be nice if the admin API covers Valkey and Redis to be finally displayed in Admin Web properly.

Given the current lack of an officially recommended Redis configuration in the documentation, but when just simply taking https://community.grommunio.com/d/426-redis-at-grommunio-documentation-for-debian11, as a base, an instanced systemd unit like redis@grommunio.service works indeed out of the box, while valkey@grommunio.service does obviously not. But when then leveraging systemd.unit Alias=redis@grommunio.service for valkey@grommunio.service, an empty label is shown in the Admin Web…which is quite unexpected!

Please add at least support for systemd.unit Alias=… to the Admin API to cover generally upcoming Redis alternatives more nicely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant