Difference between revisions of "Standard Server Configuration"

From Dryad wiki
Jump to: navigation, search
(Created page with " We create scripts and symlinks wherever possible to keep all machines using the directories/commands listed here, regardless of differences in the underlying OS. This makes sy...")
 
Line 1: Line 1:
 +
We create scripts and symlinks wherever possible to keep all machines using the directories/commands listed here, regardless of differences in the underlying OS. This makes  system maintenance much easier, and allows our scripts to work correctly on any standard Dryad system.
  
We create scripts and symlinks wherever possible to keep all machines using the directories/commands listed here, regardless of differences in the underlying OS. This makes  system maintenance much easier, and allows our scripts to work correctly on any standard Dryad system.
+
*All content is owned by the dryad user.
 
+
*DSpace/Tomcat runs as the dryad user.
*All content is owned by the dryad user.  
 
*DSpace/Tomcat runs as the dryad user.  
 
 
*All major directories are symlinked from the Dryad home directory, for easy access
 
*All major directories are symlinked from the Dryad home directory, for easy access
*The handle server should only run on production, because we don't want multiple copies registered with the root handle server.  
+
*The handle server should only run on production, because we don't want multiple copies registered with the root handle server.
*Handle prefix: 10255  
+
*Handle prefix: 10255
*DOI prefix: 10.5061  
+
*DOI prefix: 10.5061
  
 
Dryad/DSpace:
 
Dryad/DSpace:
Line 27: Line 26:
 
Maven profile:
 
Maven profile:
 
* (Dryad home)/maven/conf/settings.xml
 
* (Dryad home)/maven/conf/settings.xml
 +
 +
[[Category:Software]]
 +
[[Category:Installation and Maintenance]]
 +
[[Category:Help]]

Revision as of 12:09, 27 September 2011

We create scripts and symlinks wherever possible to keep all machines using the directories/commands listed here, regardless of differences in the underlying OS. This makes system maintenance much easier, and allows our scripts to work correctly on any standard Dryad system.

  • All content is owned by the dryad user.
  • DSpace/Tomcat runs as the dryad user.
  • All major directories are symlinked from the Dryad home directory, for easy access
  • The handle server should only run on production, because we don't want multiple copies registered with the root handle server.
  • Handle prefix: 10255
  • DOI prefix: 10.5061

Dryad/DSpace:

  • code is built to /opt/dryad (or an instance-specific directory, like dryad-demo)
  • dspace logs: /opt/dryad/log

Tomcat:

  • To restart Tomcat: (Dryad home)/bin/tomcat-restart.sh
  • Tomcat configuration: (Dryad home)/tomcat/conf
  • Tomcat logs: (Dryad home)/tomcat/logs
  • Tomcat webapps: (Dryad home)/tomcat/webapps

Postgres:

  • Run the postgres client with the "standard" dryad user and database: postgres-client.sh

Hudson/Jenkins:

Maven profile:

  • (Dryad home)/maven/conf/settings.xml