|
|
|
|
This document describes how to configure the DamageControl server.
Legend:
Won't work yet - this is how we want it to be.
The way it currently works. We'll probably move away from this.
Required steps
Set your PATH
Make sure your PATH points to the required programs:
- ruby
- cvs (if you are running against CVS)
- svn (if you are running against Subversion)
- java (if you intend DamageControl to build java projects)
- ant (if you intend DamageControl to build java projects with Ant)
- maven (if you intend DamageControl to build java projects with Maven)
- gnuplot (if you intend DamageControl to generate Statistical Graphs)
Define environment variables
- DAMAGECONTROL_HOME - should point to a folder where DamageControl will keep:
- checkout/ - Projects will be checked out here.
- log/ - Build output (stdout/stderr) will be written here.
- report/ - Various reports (HTML, RSS, Statistical Graphs will be written here.
- config/ - Individual project configuration will be stored here.
- (Any other environment variables required by the tools above in the PATH section, such as ANT_HOME, MAVEN_HOME etc.
Start the DamageControl server
Start the DamageControl server with the following command:
DamageControl will write its activity to a file called damagecontrol.log in the same directory. It might be a good idea to delete it every now and then as it might become big.
Optional steps
Apache configuration
TODO: Move this to a separate Apache document.
DAMAGECONTROL_HOME Access
It is recommended that you configure Apache so that it can serve the content under DAMAGECONTROL_HOME.
DamageControl's built-in web server will serve these pages. Configure Apache to point to DC's internal webserver for a path of your choice.
Access control
Set up access control so that authentication is needed in order to access the DamageControl web based admin console.
[ edit ]