|
|
|
|
This document describes how to install DamageControl.
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
These steps are the minimal steps required to install and run DamageControl. After you are done here you should see Server Configuration.
Install Ruby (on Linux/Unix/MacOS X only)
Get Ruby 1.8.2_pre2 or later from http://www.ruby-lang.org/
A Ruby distribution is included in the Windows installer.
Install SCM clients
You must install a client for the SCM that you intend to use DamageControl with. For example:
- CVS: http://www.cvshome.org/
- Subversion: http://subversion.tigris.org/
Download DamageControl
Download installer or archive (for Linux/Unix/MacOS X) from Downloads.
Install
Run installer (on Windows) or unpack .tar.gz (on Linux/Unix/MacOS X).
Optional steps
Install Apache HTTP Server
Only required if you need extra security. See Security and Access Control. Download Apache from http://httpd.apache.org/.
Install an IRC server
If you don't have an IRC server handy and you want DamageControl to report activity on IRC, you must install an IRC server.
Install a mail server
If you don't have a mail server (with SMTP support) handy and you want DamageControl to report build status over mail, you must install a mail server.
Set up a mailing list
The recommended way to have DamageControl report build status over mail is via a mailing list. You should make sure your SMTP server supports mailing lists. If it doesn't, you should install separate mailing list software (such as mailman) and create a list for each project. All developers on a project should be subscribed to this mailing list.
DamageControl can also send mail to individual developers.
Install Gnuplot
Only required if you want DamageControl to generate Statistical Graphs. Download Gnuplot 4.0 or later from http://gnuplot.sf.net/.
[ edit ]