Standard Server Configuration

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

Apache:
 * To restart Apache: (Dryad home)/bin/apache-restart.sh
 * Apache configuration: (Dryad home)/apache/conf
 * Apache logs: (Dryad home)/apache/logs
 * Apache static pages: (Dryad home)/apache/htdocs

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

Hudson/Jenkins:
 * installed at /jenkins on the primary machine name (e.g., https://datadryad.org/jenkins)
 * Hudson/Jenkins runs on top of Jetty, so it can be restarted independently of Tomcat
 * To restart Jetty: (Dryad home)/bin/jetty-restart.sh

Maven profile:
 * (Dryad home)/maven/conf/settings.xml