Difference between revisions of "Standard Server Configuration"

From Dryad wiki
Jump to: navigation, search
 
(3 intermediate revisions by the same user not shown)
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.
+
*All content is owned by, and processes run by, the primary login account for the machine. This is either 'dryad' or 'ubuntu'.
*DSpace/Tomcat runs as the dryad user.
+
*All major directories are symlinked from the primary login's 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
 
*DOI prefix: 10.5061
 
  
 
Dryad/DSpace:
 
Dryad/DSpace:
* code is built to /opt/dryad (or an instance-specific directory, like dryad-demo)
+
* code is built to /opt/dryad
 
* dspace logs: /opt/dryad/log
 
* dspace logs: /opt/dryad/log
  
Line 20: Line 17:
 
Apache:
 
Apache:
 
* To restart Apache: (Dryad home)/bin/apache-restart.sh
 
* To restart Apache: (Dryad home)/bin/apache-restart.sh
* To put the maintenance page in place: (Dryad home)/bin/apache-maint-on.sh
 
* To remove the maintenance page: (Dryad home)/bin/apache-maint-off.sh
 
 
* Apache configuration: (Dryad home)/apache/conf
 
* Apache configuration: (Dryad home)/apache/conf
 
* Apache logs: (Dryad home)/apache/logs
 
* Apache logs: (Dryad home)/apache/logs
Line 28: Line 23:
 
Postgres:
 
Postgres:
 
* Run the postgres client with the "standard" dryad user and database: postgres-client.sh
 
* 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)
 
  
 
Maven profile:
 
Maven profile:

Latest revision as of 12:33, 21 February 2018

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, and processes run by, the primary login account for the machine. This is either 'dryad' or 'ubuntu'.
  • All major directories are symlinked from the primary login's 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.

Dryad/DSpace:

  • code is built to /opt/dryad
  • 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

Maven profile:

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