Redmine

h1. HowTos

h2. Customizing Redmine

[[HowTo translate Redmine in your own language]]

[[HowTo create a custom Redmine theme]]

h2. Installation and setup

[[HowTo run Redmine with a Mongrel cluster]]

[[HowTo configure Redmine to mail to MS Exchange server]]

[[HowTo Install Redmine in a home directory on Debian]]

h2. Misc

[[HowTo Mylyn|How to connect a Mylyn repository to Redmine]]

h2. Advanced Subversion integration

Those HowTos are intended for those who want to automate SVN repositories creation and rights management. They require some system administration skills.

_Note: They are useless for those who simply want to browse existing repositories from within Redmine (like "this":http://www.redmine.org/repositories/show/1). To do so, make sure that the svn binaries are installed on the Redmine host and go to the project settings to configure the path to the repository._

There's basically two ways to automate SVN repositories management:

* using apache/mod_dav_svn/mod_perl

* using pam modules and nss (the historical one)

h3. Using apache/mod_dav_svn/mod_perl

Basically, the first way is handled only by apache/mod_dav_svn and mod_perl, it should work on windows and unix. You need moderate apache skills. It is far simpler and faster to configure and, unless you have very big repositories, many repositories or you really don't want to use mod_perl, is the best way (at least imho).

To follow the prefered first way:

* Step 1: [[Automating repository creation]]

* Step 2: [[Repositories access control with apache, mod_dav_svn and mod_perl]]

h3. Using pam modules and nss

The second way means configuring pam modules to allow project members read/write access, svnserve to allow anonymous users to read public projects and apache/mod_dav to allow redmine browsing. It works only on unix with pam modules and a MySQL database. You need quite some large sysadmin skills.

If you want to follow the hard way: [[HowTo to handle SVN repositories creation and access control with Redmine]]