You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/sphinx-guides/source/installation/prerequisites.rst
+29-25Lines changed: 29 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ After following all the steps below, you can proceed to the :doc:`installation-m
14
14
Linux
15
15
-----
16
16
17
-
We assume you plan to run your Dataverse installation on Linux and we recommend RHEL or a derivative such as RockyLinux or AlmaLinux, which is the distribution family tested by the Dataverse Project team. Please be aware that while EL8 (RHEL/derivatives) is the recommended platform, the steps below were orginally written for EL6 and may need to be updated (please feel free to make a pull request!). A number of community members have installed the Dataverse Software in Debian/Ubuntu environments.
17
+
We assume you plan to run your Dataverse installation on Linux and we recommend RHEL or a derivative such as Rocky Linux, which is the distribution family tested by the Dataverse Project team. These instructions are written for RHEL9 and derivatives, but Dataverse is known to work well in Debian, Ubuntu, and most any modern Linux distribution.
18
18
19
19
Java
20
20
----
@@ -28,9 +28,9 @@ The Dataverse Software should run fine with only the Java Runtime Environment (J
28
28
29
29
The Oracle JDK can be downloaded from https://www.oracle.com/technetwork/java/javase/downloads/index.html
30
30
31
-
On a RHEL/derivative, install OpenJDK (devel version) using yum::
31
+
On a RHEL/derivative OS, install OpenJDK (devel version) using dnf::
32
32
33
-
# sudo yum install java-17-openjdk
33
+
# sudo dnf install java-17-openjdk
34
34
35
35
If you have multiple versions of Java installed, Java 17 should be the default when ``java`` is invoked from the command line. You can test this by running ``java -version``.
36
36
@@ -106,14 +106,14 @@ Installing PostgreSQL
106
106
107
107
*For example*, to install PostgreSQL 16 under RHEL9/derivative::
For RHEL8/derivative the process would be identical, except for the first two commands: you would need to install the "EL-8" yum repository configuration and run ``yum makecache`` instead.
116
+
You may need to disable the OS's built-in postgresql module with ``dnf -qy module disable postgresql``.
117
117
118
118
Configuring Database Access for the Dataverse Installation (and the Dataverse Software Installer)
@@ -147,7 +147,7 @@ Configuring Database Access for the Dataverse Installation (and the Dataverse So
147
147
148
148
The file ``postgresql.conf`` will be located in the same directory as the ``pg_hba.conf`` above.
149
149
150
-
- **Important: PostgreSQL must be restarted** for the configuration changes to take effect! On RHEL7/derivative and similar (provided you installed Postgres as instructed above)::
150
+
- **Important: PostgreSQL must be restarted** for the configuration changes to take effect! On RHEL9/derivative and similar (provided you installed Postgres as instructed above)::
151
151
152
152
# systemctl restart postgresql-16
153
153
@@ -205,7 +205,7 @@ On operating systems which use systemd such as RHEL/derivative, you may then add
205
205
206
206
Solr launches asynchronously and attempts to use the ``lsof`` binary to watch for its own availability. Installation of this package isn't required but will prevent a warning in the log at startup::
207
207
208
-
# yum install lsof
208
+
# dnf install lsof
209
209
210
210
Finally, you need to tell Solr to create the core "collection1" on startup::
211
211
@@ -278,6 +278,7 @@ Installing jq
278
278
279
279
``jq`` is a command line tool for parsing JSON output that is used by the Dataverse Software installation script. It is available in the ``appstream`` repository::
280
280
281
+
# dnf install epel-release
281
282
# dnf install jq
282
283
283
284
or you may install the latest binary for your OS and platform, available from https://github.com/jqlang/jq/releases
@@ -294,10 +295,10 @@ Installing and configuring ImageMagick
294
295
295
296
On a Red Hat or derivative Linux distribution, you can install ImageMagick with something like::
296
297
297
-
# yum install ImageMagick
298
+
# dnf install ImageMagick
298
299
299
300
(most RedHat systems will have it pre-installed).
300
-
When installed using standard ``yum`` mechanism, above, the executable for the ImageMagick convert utility will be located at ``/usr/bin/convert``. No further configuration steps will then be required.
301
+
When installed using standard ``dnf`` mechanism, above, the executable for the ImageMagick convert utility will be located at ``/usr/bin/convert``. No further configuration steps will then be required.
301
302
302
303
If the installed location of the convert executable is different from ``/usr/bin/convert``, you will also need to specify it in your Payara configuration using the JVM option, below. For example::
303
304
@@ -322,32 +323,35 @@ Installing R
322
323
323
324
For RHEL/derivative, the EPEL distribution is strongly recommended:
324
325
325
-
If :fixedwidthplain:`yum` isn't configured to use EPEL repositories ( https://fedoraproject.org/wiki/EPEL ):
326
+
If :fixedwidthplain:`dnf` isn't configured to use EPEL repositories ( https://fedoraproject.org/wiki/EPEL ):
327
+
328
+
RHEL9/derivative users can install the epel-release RPM::
Copy file name to clipboardExpand all lines: doc/sphinx-guides/source/installation/shibboleth.rst
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,26 +32,26 @@ We will be "fronting" the app server with Apache so that we can make use of the
32
32
33
33
We include the ``mod_ssl`` package to enforce HTTPS per below.
34
34
35
-
``yum install httpd mod_ssl``
35
+
``dnf install httpd mod_ssl``
36
36
37
37
Install Shibboleth
38
38
~~~~~~~~~~~~~~~~~~
39
39
40
40
Installing Shibboleth will give us both the ``shibd`` service and the ``mod_shib`` Apache module.
41
41
42
-
Install Shibboleth Yum Repo
42
+
Install Shibboleth DNF Repo
43
43
^^^^^^^^^^^^^^^^^^^^^^^^^^^
44
44
45
-
The Shibboleth project now provides `a web form <https://shibboleth.net/downloads/service-provider/RPMS/>`_ to generate an appropriate package repository for use with YUM/DNF.
45
+
The Shibboleth project now provides `a web form <https://shibboleth.net/downloads/service-provider/RPMS/>`_ to generate an appropriate package repository for use with DNF.
46
46
47
47
You'll want to copy-paste the form results into ``/etc/yum.repos.d/shibboleth.repo`` or wherever is most appropriate for your operating system.
48
48
49
-
Install Shibboleth Via Yum
49
+
Install Shibboleth Via DNF
50
50
^^^^^^^^^^^^^^^^^^^^^^^^^^
51
51
52
52
Please note that during the installation it's ok to import GPG keys from the Shibboleth project. We trust them.
53
53
54
-
``yum install shibboleth``
54
+
``dnf install shibboleth``
55
55
56
56
Configure Payara
57
57
----------------
@@ -122,7 +122,7 @@ Near the bottom of ``/etc/httpd/conf.d/ssl.conf`` but before the closing ``</Vir
122
122
123
123
You can download a :download:`sample ssl.conf file <../_static/installation/files/etc/httpd/conf.d/ssl.conf>` to compare it against the file you edited.
124
124
125
-
Note that ``/etc/httpd/conf.d/shib.conf`` and ``/etc/httpd/conf.d/shibboleth-ds.conf`` are expected to be present from installing Shibboleth via yum.
125
+
Note that ``/etc/httpd/conf.d/shib.conf`` and ``/etc/httpd/conf.d/shibboleth-ds.conf`` are expected to be present from installing Shibboleth via dnf.
126
126
127
127
You may wish to also add a timeout directive to the ProxyPass line within ssl.conf. This is especially useful for larger file uploads as apache may prematurely kill the connection before the upload is processed.
0 commit comments