Here is a comparison of Redmine/ChiliProject and Trac features:

The first thing that made me not to test Redmine/ChiliProject immediately was that it is RoR and the complexity to make it run stable under apache, but after searching a bit, I found Phusion Passenger and Ruby Enterprise, which is a very good solution to run RoR products stable under Apache, and you have the ability to run Ruby with custom user, usefull for shared environments.

Installation

1. Ruby Enterprise

   I downloaded and installer from source code, so that it’s compiled for my server and I can store it in a specific location. So, the first we have to do is download latest version from Ruby Enterprise Download page

   wget http://rubyenterpriseedition.googlecode.com/files/ruby-enterprise-1.8.7-2011.03.tar.gz
   tar zxvf ruby-enterprise-1.8.7-2011.03.tar.gz
   cd ruby-enterprise-1.8.7-2011.03
   ./installer

   Follow installer instructions, and install dependencies if needed (the installer tells us which packages we need for our Linux distro)

2. Phusion Passenger

   Next thing to do, is install the Passanger module for apache, this can be done with the passenger-install-apache2-module script available at Ruby Enterprise installation

   cd /opt/ruby-enterprise-1.8.7-2011.03/bin
   ./passenger-install-apache2-module

   This script also checks the dependencies and says what packages you need for your Linux distro

3. Apache

   Now we need to configure apache, first we need to activate and configure the passenger module

   /etc/apache2/mods-enabled/passenger.load

   LoadModule passenger_module /opt/ruby-enterprise-1.8.7-2011.03/lib/ruby/gems/1.8/gems/passenger-3.0.7/ext/apache2/mod_passenger.so

   /etc/apache2/mods-enabled/passenger.conf

   <ifmodule mod_passenger.c>
     PassengerRoot /opt/ruby-enterprise-1.8.7-2011.03/lib/ruby/gems/1.8/gems/passenger-3.0.7
     PassengerRuby /opt/ruby-enterprise-1.8.7-2011.03/bin/ruby
    
     PassengerFriendlyErrorPages Off
     PassengerUserSwitching On
     PassengerDefaultUser www-data
     PassengerDefaultGroup www-data
   </ifmodule>

   And the last thing is configure a vhost under which we will run this ChiliProject installation

   /etc/apache2/sites-enabled/chiliproject

   NameVirtualHost *:443
   <virtualhost *:443>
   	SSLEngine on
    
   	SSLCertificateFile    /etc/apache2/ssl/server.crt
   	SSLCertificateKeyFile /etc/apache2/ssl/server.key
    
   	<ifmodule mod_passenger.c>
   		PassengerUser chiliproject
   		PassengerGroup chiliproject
   	</ifmodule>
    
           ServerAdmin webmaster@chiliproject.org
   	ServerName chiliproject.org
    
   	DocumentRoot /home/chiliproject/public
   	<directory />
   		Options -MultiViews
   		AllowOverride All
   	< /Directory>
    
   	ErrorLog /var/log/apache2/chiliproject-error.log
    
   	CustomLog /var/log/apache2/chiliproject-access.log combined
   </virtualhost>

4. ChiliProject

   First install needed gems

   /opt/ruby-enterprise-1.8.7-2011.03/bin/gem install -v=0.4.2 i18n
   /opt/ruby-enterprise-1.8.7-2011.03/bin/gem install -v=1.0.1 rack
   /opt/ruby-enterprise-1.8.7-2011.03/bin/gem install mysql

   Download the last available ChiliProject version from ChiliProject Files Page

   wget https://www.chiliproject.org/attachments/download/99/chiliproject-1.4.0.tar.gz
   tar zxvf chiliproject-1.4.0.tar.gz
   mv chiliproject-1.4.0 /home/chiliproject

   Create the mysql database and user for ChiliProject

   CREATE DATABASE chiliproject CHARACTER SET utf8 COLLATE utf8_unicode_ci;
   GRANT ALL privileges ON chiliproject.* TO 'chiliproject'@'localhost' IDENTIFIED BY 'my_password';

   Configure ChiliProject Database Connection

   mv config/database.yml.example config/database.yml

   production:
     adapter: mysql
     database: chiliproject
     host: localhost
     username: chiliproject
     password: my_password

   Now initialize ChiliProject (session Store, DB Tables, DB Default Data

   /opt/ruby-enterprise-1.8.7-2011.03/bin/rake generate_session_store
   RAILS_ENV=production /opt/ruby-enterprise-1.8.7-2011.03/bin/rake db:migrate
   RAILS_ENV=production /opt/ruby-enterprise-1.8.7-2011.03/bin/rake redmine:load_default_data

   And the last thing we need to do before we can restart apache and begin to use the new installed ChiliProject, we need to create the chiliproject user

   adduser --home /home/chiliproject --shell /bin/false --no-create-home chiliproject
   chown -R chiliproject:chiliproject /home/chiliproject

5. (Optinal) Rmagick

   If we would like to enable Gantt export to png image we need to install Rmagick (available as gem). First we need to install imagemagick ang graphicsmagick dev packages and then we can install the rmagick gem.

   apt-get install libmagickcore-dev libgraphicsmagick1-dev libmagickwand-dev
   /opt/ruby-enterprise-1.8.7-2011.03/bin/gem install rmagick

Now we only need to restart Apache and load ChiliProject in our Browser. The default user is admin/admin

First of all we need to install needed packages

apt-get install libapache2-mod-wsgi python-virtualenv python-setuptools

Once we have installed the required packages proceed to create the Python environment

mkdir /usr/local/trac
cd /usr/local/trac
virtualenv python

We now have the isolated Python environment locate under /usr/local/trac/python.

To make possible to use easy_install with repositories we need to upgrade easy_install. I use this to install Trac plugins directly from SVN.

/usr/local/trac/python/bin/easy_install -U trunk

We now can install trac 0.12 using the 0.12b1 SVN Tag (http://svn.edgewall.com/repos/trac/tags/trac-0.12b1 or Trac==0.12b1) or directly from SVN Trunk:

/usr/local/trac/python/bin/easy_install http://svn.edgewall.org/repos/trac/trunk

This will download and install the latest trunk version for Trac.

To have webaccess to the Trac projects, we need a .wsgi script, were we define where our local python environment is located:

# Not needed if mod_wsgi >= 3.0
import sys
sys.stdout = sys.stderr
 
# Load Trac
import trac.web.main
application = trac.web.main.dispatch_request

And finally we need to configure apache. If you want only one Trac project, you should define trac.env to the location of your trac, but if you want multiproject support, you must use trac.env_parent_dir (this is what I used)

<virtualhost *:80>
    ServerName trac.dns.com
 
    DocumentRoot /usr/local/trac/htdocs
    ErrorLog /var/log/apache2/trac-error.log
    CustomLog /var/log/apache2/trac-access.log combined
 
    # Trac Auth
    <location />
        AuthType Basic
        AuthName "Trac"
        AuthUserFile /usr/local/trac/.htpasswd
        Require valid-user
    < /location>
 
    #Trac
    #Define ProcessGroup with user and group under which it should run
    WSGIDaemonProcess trac user=trac group=trac python-path=/usr/local/trac/python/lib/python2.5/site-packages python-eggs=/usr/local/trac/python/cache
    WSGIScriptAlias / /usr/local/trac/htdocs/trac.wsgi
 
    <directory /usr/local/trac/htdocs>
        WSGIProcessGroup trac
        WSGIApplicationGroup %{GLOBAL}
        SetEnv trac.env_parent_dir /usr/local/trac/projects
    </directory>
</virtualhost>

We need to create the user and change the permissions for /usr/local/trac for that user trac

adduser --home /usr/local/trac --shell /bin/false --no-create-home trac
chown -R trac:trac /usr/local/trac

If you get an error “ImportError: No module named simplejson” just install it using easy_install

/usr/local/trac/python/bin/easy_install simplejson

apt-get install trac subversion apache2 subversion libapache2-svn libapache2-mod-python2.3

Una vez descargado e instalado creamos el certificado necesario para usar tanto trac y subversion bajo https. Entra en el directorio /etc/apache2/ssl y ejecuta lo siguiente:

openssl genrsa -des3 -out server.key 1024
openssl req -new -key server.key -out server.csr
cp server.key server.key.org
openssl rsa -in server.key.org -out server.key
openssl x509 -req -days 365 -in server.csr -signkey server.key -out server.crt

Ahora ya tenemos listo los certificados, asi que ahora solo nos queda configurar el apache. Yo he creado un trac.dominio.ext y un svn.dominio.ext para hacer esto, pero esto va a gusto de cada uno. Yo como uso dos subdominios distintos, lo tengo en ficheros separados.

Primero editaremos el trac, asi que creamos el fichero /etc/apache2/sites-available/trac.domain.ext

NameVirtualHost *:443
<VirtualHost *:443>
#Activate SSL
SSLEngine on
 
SSLCertificateFile    /etc/apache2/ssl/server.crt
SSLCertificateKeyFile /etc/apache2/ssl/server.key
 
#VirtualHost Servername
ServerName trac.domain.ext
ServerAdmin trac@domain.ext
 
DocumentRoot /opt/projects/trac
 
#Authentication
<Location />
AuthType Basic
AuthName "Trac"
AuthUserFile /opt/projects/.htpasswd
Require valid-user
 
#Trac
SetHandler mod_python
PythonHandler trac.web.modpython_frontend
PythonOption TracEnvParentDir /opt/projects/trac/
PythonOption TracUriRoot /
 
</Location>
</VirtualHost>

El fichero no necesita demasiada explicacion, simplemente le decimos que active el SSL, que pida autentificacion y cargamos el modulo del trac y le especificamos el path de donde estan todos nuestros proyectos.

Ahora vamos con el fichero /etc/apache2/sites-available/svn.domain.ext

NameVirtualHost *:443
<VirtualHost *:443>
#Activate SSL
SSLEngine on
 
SSLCertificateFile    /etc/apache2/ssl/server.crt
SSLCertificateKeyFile /etc/apache2/ssl/server.key
 
#VirtualHost Servername
ServerName svn.domain.ext
ServerAdmin svn@domain.ext
 
DocumentRoot /opt/projects/svn
<Location />
DAV svn
 
#Authentication
AuthType Basic
AuthName "Subversion"
AuthUserFile /opt/projects/.htpasswd
Require valid-user
 
#Subversion
SVNParentPath /opt/projects/svn
SVNListParentPath on
SVNAutoVersioning On
</Location>
 
<LocationMatch "/.+">
#Subversion permission file
AuthzSVNAccessFile /opt/projects/svn/.htpasswd
</LocationMatch>
</VirtualHost>

Es importante separar el AuthzSVNAccessFile de <Location /> ya que sino no listara todos los proyectos en http://svn.domain.ext/ por problemas de permisos.

Ahora que tenemos estos ficheros listos, hay que activar el modulo de ssl en el apache2 y los dos dominios.

vi /etc/apache2/ports.conf

<IfModule mod_ssl.c>
Listen 443
</IfModule>

cd /etc/apache2/mods-enabled
ln -s /etc/apache2/mods-available/dav.load .
ln -s /etc/apache2/mods-available/dav_svn.load .
ln -s /etc/apache2/mods-available/mod_python.load .
ln -s /etc/apache2/mods-available/ssl.conf .
ln -s /etc/apache2/mods-available/ssl.load .
 
cd /etc/apache2/sites-enabled
ln -s /etc/apache2/sites-available/svn.domain.ext 001-svn.domain.ext
ln -s /etc/apache2/sites-available/trac.domain.ext 001-trac.domain.ext

Ahora vamos a crear un proyecto de prueba

mkdir -p /opt/projects/svn
mkdir -p /opt/projects/trac
svnadmin create /opt/projects/svn/NewProject
trac-admin /opt/projects/trac/NewProject initenv

Project Name [My Project]> NewProject
Database connection string [sqlite:db/trac.db]>
Path to repository [/var/svn/test]> /opt/projects/svn/NewProject
Templates directory [/usr/share/trac/templates]>
Creating and Initializing Project
Configuring Project
trac.repository_dir
trac.database
trac.templates_dir
project.name
Installing default wiki pages
..............

Ahora creamos los ficheros de acceso de usuarios.

[Repositorio:/Path]
user = [ [r[w]]]

Por ejemplo, queremos que el user1 pueda leer y escribir, el user2 leer, y anonymous nada (no deberia haber anonymous ya que el htpasswd no los deja pasar, pero siempre viene bien protegerse por si acaso), el fichero quedaria asi

[NewProject:/]
user1 = rw
user2 = r
* =

Ahora ya tenemos todo listo, podemos instalar el modulo TracWebAdmin para que sea mas facil la administracion del trac.
]]>
			http://p0l0.binware.org/index.php/2006/10/03/multiples-proyectos-con-trac-y-svn-usando-https/feed/
		0