Talk:Redis

From ArchWiki

Redis-Json

We should probably add a note about installing redis-rejsonAUR to enable redis-json. Also, we should remove redis-jsonAUR or add a note not to use it, as the maintainer stopped maintaining it. Tsangares (talk) 00:40, 31 October 2023 (UTC)Reply

Do you have any support link about the stopped maintainess of redis-json. It seems to have new release monthes ago. See: https://github.com/RedisJSON/RedisJSON/releases/tag/v2.6.4 Fengchao (talk) 13:56, 2 November 2023 (UTC)Reply
I am noting that there are two AUR repositories for json functionality in redis and one is maintained redis-rejsonAUR:Maintained redis-jsonAUR: Orphaned. But the maintainer seems competent so idk why. I see that redis-jsonAUR is on version 2.4.2-2 and has been flagged out of date for about 3 months, whereas redis-rejsonAUR is mostly up-to-date (currently on version 2.6.4-1). The User for redis-jsonAUR is Greyltc which maintains a lot of packages. But this one was uploaded once and never updated. So I am not sure. But the repository for redis-rejsonAUR is being maintained and talked about. Tsangares (talk) 00:04, 14 November 2023 (UTC)Reply

Valkey to replace Redis in the [extra] Repository

Given that `valkey` will soon be replacing `redis` in [extra]1, and that Valkey is a fork of Redis...

What's the best way to introduce the Valkey wiki page? My initial thought was to create a clone of the Redis wiki page (since much if not all of the content is applicable to Valkey) and change references from Redis, to Valkey, however, after speaking with several individuals it seems this may not be the best idea. Should this wiki page simply be renamed from Redis to Valkey and the content of the page be updated to reflect the change? Thoughts? Suggestions?

1 https://lists.archlinux.org/archives/list/arch-dev-public@lists.archlinux.org/thread/2ERGX565GSSBUMADBG7DQJYNPJD5GUXD/ AndrewSC (talk) 14:52, 15 August 2024 (UTC)Reply

+1 for rename it to valkey and mention the announcement. --Fengchao (talk) 13:38, 14 September 2024 (UTC)Reply