Page History

...

• A server snapshot (backup) is generated nightly
  
  • Snapshots from the last 4 nights are kept
  • Every Sunday a weekly snapshot is generated and kept for two weeks
  • On the first of the month a monthly snapshot is generated and kept for two months

...

• Tomcat is configured to run on port 80
  
  • It is using 'jsvc' to start as 'root' and then switch to being owned by 'dspace'
  • Tomcat's startup settings are all located in ~dspace/.profile
• DSpace Webapps are run from ~/dspace/webapps/ (configured in Tomcat's server.xml)
• The main "splash" page (http://demo.dspace.org) is generated served by Tomcat and is located at: ~/tomcat/webapps/ROOT/index.html
  
  • Its content is also managed via the GitHub Repository at: http://github.com/DSpace/demo.dspace.org
  • Info on updating & pushing to GitHub can be found in the README at https://github.com/DSpace/demo.dspace.org

...

• The JavaDocs pages (http://demo.dspace.org/javadocs/) are generated static pages served by Tomcat and are located at: ~/tomcat/webapps/javadocs/
• These JavaDocs can be regenerated at any time by running the following (from the root source directory, [dspace-source]):
  

  • mvn javadoc:aggregate

  • The "javadoc:aggregate" command generates a single set of javadocs which aggregate the APIs of all DSpace modules.  See http://maven.apache.org/plugins/maven-javadoc-plugin/plugin-info.html
  • NOTE: We've encountered some oddities with the results when this is run from demo.dspace.org itself (the resulting CSS isn't applied).  So, it's recommended to run this command from your local machine. It worked fine on 2 machines running Java 6, Maven 2.2.1 and 3.0.3, respectively. It didn't work on demo, which was running Java 7 and Maven 2.2.1.

...