From d6c4683d01d7eb9bb7b7797d44be0b938262b08d Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Mon, 12 Mar 2018 13:50:03 -0400 Subject: [PATCH] move DataCite troubleshooting to appropriate page #4419 --- doc/sphinx-guides/source/developers/dev-environment.rst | 9 --------- doc/sphinx-guides/source/developers/troubleshooting.rst | 9 +++++++++ 2 files changed, 9 insertions(+), 9 deletions(-) diff --git a/doc/sphinx-guides/source/developers/dev-environment.rst b/doc/sphinx-guides/source/developers/dev-environment.rst index 4110cb05e4e..b7e36f3c960 100755 --- a/doc/sphinx-guides/source/developers/dev-environment.rst +++ b/doc/sphinx-guides/source/developers/dev-environment.rst @@ -219,15 +219,6 @@ Geoconnect works as a middle layer, allowing geospatial data files in Dataverse As mentioned under "Architecture and Components" in the :doc:`/installation/prep` section of the Installation Guide, Geoconnect is an optional component of Dataverse, so this section is only necessary to follow it you are working on an issue related to this feature. -DataCite --------- - -If you've reconfigured from EZID to DataCite and are seeing ``Response code: 400, [url] domain of URL is not allowed`` it's probably because your ``dataverse.siteUrl`` JVM option is unset or set to localhost (``-Ddataverse.siteUrl=http://localhost:8080``). You can try something like this: - -``asadmin delete-jvm-options '-Ddataverse.siteUrl=http\://localhost\:8080'`` - -``asadmin create-jvm-options '-Ddataverse.siteUrl=http\://demo.dataverse.org'`` - ---- Previous: :doc:`intro` | Next: :doc:`troubleshooting` diff --git a/doc/sphinx-guides/source/developers/troubleshooting.rst b/doc/sphinx-guides/source/developers/troubleshooting.rst index 580f1edaeeb..3c4c079b94b 100755 --- a/doc/sphinx-guides/source/developers/troubleshooting.rst +++ b/doc/sphinx-guides/source/developers/troubleshooting.rst @@ -94,6 +94,15 @@ If you have an old copy of the database and old Solr data and want to start fres You may also find https://github.com/IQSS/dataverse/blob/develop/scripts/deploy/phoenix.dataverse.org/deploy and related scripts interesting because they demonstrate how we have at least partially automated the process of tearing down a Dataverse installation and having it rise again, hence the name "phoenix." See also "Fresh Reinstall" in the :doc:`/installation/installation-main` section of the Installation Guide. +DataCite +-------- + +If you've reconfigured from EZID to DataCite and are seeing ``Response code: 400, [url] domain of URL is not allowed`` it's probably because your ``dataverse.siteUrl`` JVM option is unset or set to localhost (``-Ddataverse.siteUrl=http://localhost:8080``). You can try something like this: + +``asadmin delete-jvm-options '-Ddataverse.siteUrl=http\://localhost\:8080'`` + +``asadmin create-jvm-options '-Ddataverse.siteUrl=http\://demo.dataverse.org'`` + ---- Previous: :doc:`dev-environment` | Next: :doc:`tips`