I vetted many of the project management tools that I've been looking at with teams at work and Redmine was the overwhelming winner. The one thing it was missing was a calendar, but we've found a makeshift way of dealing with this by inserting a static google calendar with reminders.
http://www.redmine.org/boards/1/topics/show/950
Still a work in progress but it seemed to work well enough.
Then came time to install Redmine on our production server instead of the test one. Installing Rails wasn't too hard as I found some good tutorials
http://wiki.rubyonrails.org/rails/pages/RailsOnCentos5
I had been running Redmine via lighttpd with fastcgi, but I wanted to go with Mongrel for this install as lighttpd was a bit problematic.
Good instructions on the Redmine wiki and another site
http://www.redmine.org/wiki/redmine/HowTo_run_Redmine_with_a_Mongrel_cluster
http://ubuntuforums.org/showthread.php?t=674598
Figuring out how to fire up Mongrel on boot was harder, but found that eventually too (wish I could remember where I found this one)
mkdir /etc/mongrel_cluster
ln -s /home/redmine/config/mongrel_cluster.yml /etc/mongrel_cluster/redmine.yml
cp /usr/lib/ruby/gems/1.8/gems/mongrel_cluster-1.0.5/resources/mongrel_cluster /etc/init.d/
chmod 755 /etc/init.d/mongrel_cluster
chkconfig mongrel_cluster on
Ok. Now the hard part. I knew that there would be some non-technical folks using the site, and I knew that I wanted at least logins secured with ssl. Problem is that Redmine runs under a subdomain, and in fact in this case it was a subdomain of a name based virtual host. I had tried once before to configure certificates to work in this case and failed. But I wanted to try again.
This time I won.
First I had to edit ssl.conf and add in the virtual host (as in the httpd.conf file) and also added this line to take name based virtual hosts
NameVirtualHost *:443
Then I edited openssl.cnf
Under both [usr_cert] AND [ v3_req ]
I added
subjectAltName = @alt_names
and
[alt_names]
DNS.1 = name1.com
DNS.2 = name2.com
DNS.3 = sub.name2.com
where name1.com is the owner's name as well (in the certificates, essentially the FQDN).
Then I found this post that took me through the rest (with the exception of the path to the certificates, which is in /etc/pki/tls in Centos/RHEL 5).
http://nixcraft.com/server-configuration-tutorials/3075-postfix-mail-server-create-self-signed-ssl-certificates-cent-os-redhat-linux.html
Did a little magic with the SVN repository as I had before, and voila it is up and running.
http://www.redmine.org/boards/1/topics/show/950
Still a work in progress but it seemed to work well enough.
Then came time to install Redmine on our production server instead of the test one. Installing Rails wasn't too hard as I found some good tutorials
http://wiki.rubyonrails.org/rails/pages/RailsOnCentos5
I had been running Redmine via lighttpd with fastcgi, but I wanted to go with Mongrel for this install as lighttpd was a bit problematic.
Good instructions on the Redmine wiki and another site
http://www.redmine.org/wiki/redmine/HowTo_run_Redmine_with_a_Mongrel_cluster
http://ubuntuforums.org/showthread.php?t=674598
Figuring out how to fire up Mongrel on boot was harder, but found that eventually too (wish I could remember where I found this one)
mkdir /etc/mongrel_cluster
ln -s /home/redmine/config/mongrel_cluster.yml /etc/mongrel_cluster/redmine.yml
cp /usr/lib/ruby/gems/1.8/gems/mongrel_cluster-1.0.5/resources/mongrel_cluster /etc/init.d/
chmod 755 /etc/init.d/mongrel_cluster
chkconfig mongrel_cluster on
Ok. Now the hard part. I knew that there would be some non-technical folks using the site, and I knew that I wanted at least logins secured with ssl. Problem is that Redmine runs under a subdomain, and in fact in this case it was a subdomain of a name based virtual host. I had tried once before to configure certificates to work in this case and failed. But I wanted to try again.
This time I won.
First I had to edit ssl.conf and add in the virtual host (as in the httpd.conf file) and also added this line to take name based virtual hosts
NameVirtualHost *:443
Then I edited openssl.cnf
Under both [usr_cert] AND [ v3_req ]
I added
subjectAltName = @alt_names
and
[alt_names]
DNS.1 = name1.com
DNS.2 = name2.com
DNS.3 = sub.name2.com
where name1.com is the owner's name as well (in the certificates, essentially the FQDN).
Then I found this post that took me through the rest (with the exception of the path to the certificates, which is in /etc/pki/tls in Centos/RHEL 5).
http://nixcraft.com/server-configuration-tutorials/3075-postfix-mail-server-create-self-signed-ssl-certificates-cent-os-redhat-linux.html
Did a little magic with the SVN repository as I had before, and voila it is up and running.
Leave a comment