written by cail • posted in How-To • 564 views 1 comment

I installed redmine 1.3.2 couple months ago following the following two posts

I didn't go with the 1.4.x version of redmine because there is no good tutorial on how to set it up with nginx.

It runs on nginx http server. Uses mongrel to serve the redmine. Uses supervisor to restart the mongrel process in case it dies.

However, a recent update just broke it.

After digging the installing note, I figured out that the unsupported rubygems is the reason. For 1.3.x redmine, supported rubygems versions must be <= 1.7.x

Once knowing that, it was an easy fix then.

apt-get update
apt-get upgrade
apt-get install wget build-essential ruby1.8 ruby1.8-dev irb1.8 rdoc1.8 zlib1g-dev libopenssl-ruby1.8 libopenssl-ruby libzlib-ruby libssl-dev libpcre3-dev
wget http://production.cf.rubygems.org/rubygems/rubygems-1.7.2.tgz
tar -zxvf rubygems-1.7.2.tgz
cd ./rubygems-1.7.2/
ruby setup.rb
ln -s /usr/bin/gem1.8 /usr/bin/gem

Check gems by

gem list

I installed mongrel, mysql, rails, rack, rake, etc, all via gem install with versions specified. You may find the following commands handy

gem install -v=2.3.14 rails
gem install rack -v=1.1.1
gem install rake -v0.8.7
gem install mongrel
gem install mysql

On the first start, you might find out that you need to install more gems

cd /var/www/redmine
rake generate_session_store
RAILS_ENV=production rake db:migrate
RAILS_ENV=production rake redmine:load_default_data
ruby script/server -e production

Remember, do not update rubygems! The code below is really bad. Since we didn't install gems via apt-get, apt-get upgrade should be OK.

gem update --system

Previous:
Next:

Leave a Reply

QR code of this post

blog by cail