chore: request #44079 Switch over to Valkey as the recommended Redis store

Author: LeSuisse

languages/en/administration-guide/system-administration/backup.rst

@@ -50,7 +50,7 @@ Tuleap data paths backup
 You need to save the following directories:
 
   - /etc/nginx
-  - /etc/redis
+  - /etc/valkey
   - /etc/tuleap
   - /var/lib/gitolite
   - /var/lib/tuleap
@@ -179,7 +179,7 @@ Example of bind mounts via local fstab
 .. code-block:: bash
 
     /data/etc_nginx /etc/nginx none bind,nofail 0 0
-    /data/etc_redis /etc/redis none bind,nofail 0 0
+    /data/etc_valkey /etc/valkey none bind,nofail 0 0
     /data/etc_tuleap /etc/tuleap none bind,nofail 0 0
     /data/var_lib_gitolite /var/lib/gitolite none bind,nofail 0 0
     /data/var_lib_mysql /var/lib/mysql none bind,nofail 0 0

languages/en/administration-guide/system-administration/monitoring-with-prometheus.rst

@@ -21,8 +21,8 @@ documented in their respective documentations.
 Configuration of Tuleap
 -----------------------
 
-First step is to install a Redis server and to configure Tuleap to use it,
-checkout the :ref:`Redis installation guide<installation_redis>`.
+First step is to install a Valkey server and to configure Tuleap to use it,
+checkout the :ref:`Valkey installation guide<installation_valkey>`.
 
 After having installed and activated ``tuleap-plugin-prometheus-metrics`` rpm, you need to setup a password to access the
 data (by default data are private and there is no ways to make them accessible anonymously). To do so, you need to write

languages/en/conf.py

@@ -296,7 +296,8 @@
     "user-guide/trackers/usage/markdown.rst": "user-guide/writing-in-tuleap.rst",
     "user-guide/my-personal-dashboard.rst": "user-guide/user/dashboard.rst",
     "installation-guide/intro.rst": "install.rst",
-    "administration-guide/system-administration/backend-workers.rst": "installation-guide/step-by-step/redis-configuration.rst",
+    "administration-guide/system-administration/backend-workers.rst": "installation-guide/step-by-step/valkey-configuration.rst",
+    "installation-guide/step-by-step/redis-configuration.rst": "installation-guide/step-by-step/valkey-configuration.rst",
     "installation-guide/import.rst": "administration-guide/projects-management/export-import/import-from-other-tools.rst",
     "installation-guide/ansible-installation.rst": "install.rst",
     "installation-guide/ansible/installation.rst": "install.rst",

languages/en/deployment-guide/12.x.rst

@@ -129,7 +129,7 @@ Tuleap 12.5
 Setting ``sys_async_emails`` is no more used
 --------------------------------------------
 
-Tracker notifications are now always sent asynchronously as soon as Tuleap detects :ref:`backend workers<installation_redis>`.
+Tracker notifications are now always sent asynchronously as soon as Tuleap detects :ref:`backend workers<installation_valkey>`.
 You can safely remove this setting from your ``/etc/tuleap/conf/local.inc`` file.
 
 Tuleap 12.4

languages/en/deployment-guide/15.x.rst

@@ -147,7 +147,7 @@ to adapt them for the new configuration at ``/etc/opt/remi/php82/php-fpm.d/tulea
 ------------------------------------------------------
 
 The configuration variable ``$sys_nb_backend_workers``,
-used for asynchronous job processing (see :ref:`backend workers guide<installation_redis>`),
+used for asynchronous job processing (see :ref:`backend workers guide<installation_valkey>`),
 is now set via ``tuleap config-set``.
 
 It is recommended to remove it from ``/etc/tuleap/conf/local.inc``. If you had set it specifically

languages/en/deployment-guide/9.x.rst

@@ -97,7 +97,7 @@ Backend email notifications
 In order to simplify Tuleap stack, the queue management for email notification that was based in 9.17 on RabbitMQ as been
 changed to rely on Redis instead. If you already have a Redis server installed and configured the change will be transparent.
 
-Otherwise you will need to setup a Redis server, checkout :ref:`backend workers guide<installation_redis>`.
+Otherwise you will need to setup a Redis server, checkout :ref:`backend workers guide<installation_valkey>`.
 
 If do not use the backend email notifications, you can safely ignore this step while
 upgrading.

languages/en/installation-guide/docker/docker_standalone.rst

@@ -1,7 +1,7 @@
 Docker Standalone
 =================
 
-For anything but tests, you should have a dedicated MySQL (**version 8.0**) and Redis (last stable recommended) databases.
+For anything but tests, you should have a dedicated MySQL (**version 8.0**) and Redis or Valkey (last stable recommended) databases.
 
 At first run you will need to provide some information about the platform you want to deploy:
 

languages/en/installation-guide/docker/images-configuration.rst

@@ -38,7 +38,7 @@ Site administration
 Redis
 #####
 
-* ``TULEAP_FPM_SESSION_MODE``: you can set it to ``redis`` so php sessions will be stored in a `Redis <https://redis.io>`_ K/V store.
+* ``TULEAP_FPM_SESSION_MODE``: you can set it to ``redis`` so php sessions will be stored in a `Redis <https://redis.io>`_ or `Valkey <https://valkey.io/>`_ K/V store.
 * ``TULEAP_REDIS_SERVER``: needed if you set ``redis`` for ``TULEAP_FPM_SESSION_MODE``.
 * ``TULEAP_REDIS_PORT``: needed if redis is listening on port that is not ``6379`` (the default).
 * ``TULEAP_REDIS_PASSWORD``: needed if redis requires a password.

languages/en/installation-guide/step-by-step/install-packages.rst

@@ -36,7 +36,7 @@ Create a file ``/etc/yum.repos.d/tuleap.repo`` with the following content:
 ::
 
     dnf install -y mysql-server \
-    redis \
+    valkey \
     tuleap \
     tuleap-plugin-agiledashboard \
     tuleap-plugin-api-explorer \

languages/en/installation-guide/step-by-step/introduction.rst

@@ -15,7 +15,7 @@ Table of contents:
    setup
    tls-configuration
    mail-configuration
-   redis-configuration
+   valkey-configuration
    first-connection
    install-plugins
    upgrade