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/config.rst
+45-14Lines changed: 45 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1435,32 +1435,63 @@ It's also possible to change these values by stopping Payara, editing ``payara5/
1435
1435
dataverse.fqdn
1436
1436
++++++++++++++
1437
1437
1438
-
If the Dataverse installation has multiple DNS names, this option specifies the one to be used as the "official" hostname. For example, you may want to have ``dataverse.example.edu``, and not the less appealing ``server-123.example.edu`` to appear exclusively in all the registered global identifiers, etc.
1439
-
1440
-
The password reset feature requires ``dataverse.fqdn`` to be configured.
1441
-
1442
-
Configuring ``dataverse.fqdn`` is not enough. Read on for the importance of also setting ``dataverse.siteUrl``.
1438
+
If the Dataverse installation has multiple DNS names, this option specifies the one to be used as the "official"
1439
+
hostname. For example, you may want to have ``dataverse.example.edu``, and not the less appealing
1440
+
``server-123.example.edu`` to appear exclusively in all the registered global identifiers, etc.
1441
+
1442
+
- Email confirmation links
1443
+
- Password reset links
1444
+
- Generating a Private URL
1445
+
- PID minting
1446
+
- Exporting to Schema.org format (and showing JSON-LD in HTML's <meta/> tag)
1447
+
- Exporting to DDI format
1448
+
- Which Dataverse installation an "external tool" should return to
1449
+
- URLs embedded in SWORD API responses
1450
+
- ...
1451
+
1452
+
Usually it will follow the pattern ``https://<full-qualified-domain-name>/<some-place-to-go-to>``.
1453
+
*Only* the FQDN part of your Dataverse installation URL can be determined by setting ``dataverse.fqdn``.
1454
+
1455
+
**Notes:**
1456
+
1457
+
- The URL will default to using ``https://`` and no additional port information. If that does not suit your setup, you
1458
+
can define an additional option, ``dataverse.siteUrl``, :ref:`explained below <dataverse.siteUrl>`, which always
1459
+
takes precedence.
1460
+
- Can also be set via *MicroProfile Config API* sources, e.g. the environment variable ``DATAVERSE_FQDN``.
1461
+
Defaults to ``localhost`` when used with ``mp.config.profile=ct``
1443
1462
1444
1463
.. _dataverse.siteUrl:
1445
1464
1446
1465
dataverse.siteUrl
1447
1466
+++++++++++++++++
1448
1467
1449
-
``dataverse.siteUrl`` is used to configure the URL for your Dataverse installation that you plan to advertise to your users. As explained in the :ref:`installation <importance-of-siteUrl>` docs, this setting is critical for the correct operation of your installation.
1450
-
1451
-
For example, your site URL could be https://dataverse.example.edu
1468
+
``dataverse.siteUrl`` is used to configure the URL for your Dataverse installation that you plan to advertise to your
1469
+
users. As explained in the :ref:`installation <importance-of-siteUrl>` docs, this setting is critical for the correct
1470
+
operation of your installation. For example, your site URL could be https://dataverse.example.edu . That is, even though
1471
+
the server might also be available at uglier URLs such as https://server-123.example.edu, the site URL is the
1472
+
"official" URL.
1452
1473
1453
-
That is, even though the server might also be available at uglier URLs such as https://server-123.example.edu the site URL is the "official" URL.
1474
+
That said, some environments may require using a different URL pattern to access your installation. You might need to
1475
+
use HTTP without "S", a non-standard port and so on. This is especially useful in development or testing environments.
1454
1476
1455
-
The ``dataverse.siteUrl`` JVM option can be configured by following the procedure under :ref:`jvm-options` or by editing ``domain.xml`` directly. You can specify the protocol, host, and port number. Your ``domain.xml`` file could look like this, for example:
1477
+
You can provide any custom tailored site URL via ``dataverse.siteUrl``, which always takes precedence.
If you wish to change your site URL by changing the domain configuration, you should edit your ``domain.xml`` directly
1481
+
to avoid problems with colons in commands. Find a line similar to
1482
+
``<jvm-options>-Ddataverse.siteUrl=https://dataverse.example.edu</jvm-options>`` and change it. You can specify the
1483
+
protocol, host, and port number and should not include a trailing slash.
1458
1484
1459
-
Note that it's also possible to use the ``dataverse.fqdn`` as a variable, if you wish. Here's an example of this as well as a custom port (which is usually not necessary):
- Remember to restart Payara after editing ``domain.xml``.
1490
+
- Can also be set via *MicroProfile Config API* sources, e.g. the environment variable ``DATAVERSE_SITEURL``.
1491
+
Defaults to ``http://${dataverse.fqdn}:8080`` when used with ``mp.config.profile=ct``
1492
+
- We are absolutely aware that it's confusing to have both ``dataverse.fqdn`` and ``dataverse.siteUrl``.
1493
+
https://github.com/IQSS/dataverse/issues/6636 is about resolving this confusion.
1462
1494
1463
-
We are absolutely aware that it's confusing to have both ``dataverse.fqdn`` and ``dataverse.siteUrl``. https://github.com/IQSS/dataverse/issues/6636 is about resolving this confusion.
0 commit comments