move DataCite troubleshooting to appropriate page #4419

IQSS · Mar 12, 2018 · d6c4683 · d6c4683
1 parent 9a79ba7
commit d6c4683
Show file tree

Hide file tree

Showing 2 changed files with 9 additions and 9 deletions.
diff --git 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
@@ -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`