chore: Clean up things related to CentOS 7 (or older) (#1458)

languages/en/administration-guide/application-management/plugins/bot-mattermost.rst

@@ -10,7 +10,7 @@ In your Tuleap, you can find the package name using:
 
 .. code-block:: bash
 
-    yum search tuleap-plugin-botmattermost
+    dnf search tuleap-plugin-botmattermost
 
 and to install the plugin you want.
 

languages/en/administration-guide/application-management/plugins/full-text-search.rst

@@ -67,7 +67,7 @@ on your server so monitor resource usage accordingly.
 Meilisearch server is installed with ``tuleap-meilisearch-server`` package. It's configuration is entirely managed by Tuleap.
 In order to install you will need to run:
 
-1. install the package: ``yum install tuleap-meilisearch-server``
+1. install the package: ``dnf install tuleap-meilisearch-server``
 2. activate fts_meilisearch plugin: either in site admin interface or with ``sudo -u codendiadm tuleap plugin:install fts_meilisearch``)
 3. redeploy conf: ``tuleap-cfg site-deploy``
 4. start Meilisearch server: ``systemctl start tuleap-meilisearch``

languages/en/administration-guide/application-management/plugins/git.rst

@@ -9,7 +9,7 @@ Setup tuleap-gitolite-membership
 
 Step 1: on the mirror, you need to setup minimal things:
 
-- install gitolite3:  ``yum install gitolite3``
+- install gitolite3:  ``dnf install gitolite3``
 - create a user gitolite: ``useradd --home /var/lib/gitolite --create-home gitolite``
 - As user ``gitolite``, generate an ssh key (ssh-keygen)
 - Setup gitolite with ``gitolite setup -pk .ssh/id_rsa.pub``
@@ -22,7 +22,7 @@ Step 2: on master, you need to create a new Mirror entry as site admin (Admin >
 
 Step 3: on the mirror, configure ``tuleap-gitolite-membership``:
 
-#. configure yum repository as in Tuleap installation for :ref:`Community Edition <tuleap_installation_install_packages>` or :ref:`Enterprise Edition <tuleap_installation_install_packages>`
+#. configure DNF repository as in Tuleap installation for :ref:`Community Edition <tuleap_installation_install_packages>` or :ref:`Enterprise Edition <tuleap_installation_install_packages>`
 #. install package: ``tuleap-gitolite-membership``
 #. update ``/etc/tuleap-gitolite-membership.ini`` and set the user/password defined in the previous section
 
@@ -229,58 +229,3 @@ logs previsously parsed won't be taken in account.
         $> su - codendiadm
         $> cd /usr/share/tuleap/
         $> ./src/utils/php-launcher.sh plugins/git/bin/import_all_giotlite3_logs.php
-
-Upgrade from gitolite2 to gitolite3
------------------------------------
-
-Pre-requisite
-~~~~~~~~~~~~~
-
-Upgrade will not work if there are bad ssh keys in your configuration.
-You should run the following commands before any upgrade:
-
-  .. sourcecode:: console
-
-      /usr/share/tuleap/src/utils/php-launcher.sh /usr/share/tuleap/tools/utils/purge_bad_sshkeys.php
-
-if there is any output wait for night run of daily compute (so keys are dumped again) or run the daily cron by hand
-
-Upgrade on CentOS 6
-~~~~~~~~~~~~~~~~~~~
-
-If you use the pullrequest plugin, it will be removed during the procedure, do not
-forget to install it back at the end with ``yum install tuleap-plugin-pullrequest``.
-
-Unless you are running in RHEL environnement that has been migrated from RHEL5,
-the command ``find /usr/com/gitolite/.gitolite -type d -exec chmod g+rx {} \;``
-might fail during the procedure because ``/usr/com/gitolite`` does not exist. It
-is not an issue, you can safely finish the migration.
-
-  .. sourcecode:: console
-
-      # as root, service tuleap stop
-      # su - gitolite
-      # git clone /var/lib/tuleap/gitolite/repositories/gitolite-admin.git
-      # su to root
-      # cp -ar /var/lib/gitolite /var/lib/gitolite.bkp
-      # yum install gitolite3
-      # yum remove gitolite
-      # cp -ar /var/lib/gitolite.bkp /var/lib/gitolite
-      # yum install tuleap-plugin-git-gitolite3
-      # cp ~codendiadm/.ssh/id_rsa_gl-adm.pub /tmp
-      # su - gitolite
-      # ln -s /var/lib/tuleap/gitolite/repositories
-      # cp -a .gitolite.rc gitolite2.rc
-      # cp -a /usr/share/tuleap/plugins/git/etc/gitolite3.rc.dist .gitolite.rc
-      # tar -czf gitolite2-logs.tgz ~/.gitolite/logs
-      # rm -rf repositories/gitolite-admin.git
-      # gitolite setup -pk /tmp/id_rsa_gl-adm.pub
-      # cd gitolite-admin
-      # gitolite push -f
-      # install -g gitolite -o gitolite -m 00755 /usr/share/tuleap/plugins/git/hooks/post-receive-gitolite /var/lib/gitolite/.gitolite/hooks/common/post-receive
-      # edit ~/.gitolite.rc and uncomment GROUPLIST_PGM line
-      # find /usr/com/gitolite/.gitolite -type d -exec chmod g+rx {} \;
-      # find /var/lib/tuleap/gitolite/repositories/ -type l \( -name "post-receive.mirrorpush" -o -name "gitolite-hooked" \)  -exec rm {} \;
-      # as root, service tuleap start
-
-Adapt ``/etc/httpd/conf.d/tuleap-plugins/git-http.conf`` with ``ScriptAlias /git/ /usr/lib/codendi/bin/gitolite3-suexec-wrapper.sh/``.

languages/en/administration-guide/application-management/plugins/svn.rst

@@ -31,21 +31,6 @@ A repository migrated will keep:
 * Immutable tags
 * Notifications
 
-Use Subversion 1.9 from WANdisco repository
--------------------------------------------
-
-.. warning::
-
-    Starting Subversion 1.8, the way paths are handled in the access file has changed.
-    Sections of the access file that might have been previously ignored will now deny
-    accesses to the repository. For more information, consult the Subversion 1.8
-    changelog: `FS paths syntax in authz access rules <https://subversion.apache.org/docs/release-notes/1.8#authz-fspath-syntax>`_.
-
-You can use the following instructions to install Subversion 1.9:
-
- 1. Install WANdisco repository on your server
- 2. Upgrade Subversion with ``yum upgrade subversion``
-
 .. _subversion-max-file-size:
 
 Define max file size

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

@@ -44,20 +44,19 @@ Tuleap can also exposes server metrics (CPU, RAM, etc) on the same end point. It
 configurations in Prometheus and you don't have to make your own reverse proxy to let Prometheus access securely to your
 server metrics.
 
-The server metrics are gathered by `node_exporter <https://github.com/prometheus/node_exporter>`_ you can either build
-it for yourself or you can use the packages provided in `community-supplied COPR repository <https://copr.fedorainfracloud.org/coprs/ibotty/prometheus-exporters/>`_.
+The server metrics are gathered by `node_exporter <https://github.com/prometheus/node_exporter>`_.
 
 The following example uses COPR repository
 
 .. sourcecode:: bash
 
-    # On RHEL/CentOS 7
-    $> curl -Lo /etc/yum.repos.d/_copr_ibotty-prometheus-exporters.repo https://copr.fedorainfracloud.org/coprs/ibotty/prometheus-exporters/repo/epel-7/ibotty-prometheus-exporters-epel-7.repo
-    $> yum install -y node_exporter
-
-    # Either run node_exporter manually (nohup node_exporter &) or create systemd service if you want node_exporter to run
-    # at server reboot
-    # $> nohup node_exporter &
+    # On RHEL/Rocky Linux/... 9
+    $> dnf install golang-github-prometheus-node-exporter
+    # Adjust the arguments used when starting the service to your liking
+    # You might want to only expose it locally with `--web.listen-address="127.0.0.1:9100"`
+    $> $EDITOR /etc/default/prometheus-node-exporter
+    # Start the service and enable it at boot time
+    $> systemctl enable --now prometheus-node-exporter
 
     $> tuleap config-set prometheus_node_exporter http://127.0.0.1:9100/metrics