ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

Forums » Discuss »

Insallation gives 403 Error for ChiliProject 2.0.0

Added by Noel Springer at 2011-07-24 09:46 am

Some background:

VPS: Debian 6 with Virtualmin Pro (VM)
This runs fcgi with suexec.

I successfully installed Redmine 1.1.3 using the VM install script and also successfully upgraded that to Redmine 1.2.1.

I am keen to get ChiliProject working especially as I see there will be up coming support for Milestones and it appears that community requested features may make it to production level more quickly.

I am attempting to get version 2.0.0 working.

I used git clone to get the code files which are located in ~/domains/<domain>/chiliproject

There were some installation problems until I got the right version of Rails by downgrading to 2.3.12.

sudo gem install rails -v 2.3.12

Also the bundle command couldn't be found since it was located here: /var/lib/gems/1.8/bin/bundle
To solve this I created a symlink for /usr/bin/bundle

ln -s /var/lib/gems/1.8/bin/bundle /usr/bin/bundle

Actually the same was necessary for gem since the exectable is gem1.8

ln -s /usr/bin/gem1.8 /usr/bin/gem

Running "bundle install" produced an error since the Magick-config or GraphicsMagick-config could not be found, even though I have ImageMagick installed. I decided to leave out RMagick and finally re-ran the bundle command as:

bundle install --without=rmagick

The bundle was then installed successfully and I could move on to setting up the database and database.yml and configuration.yml files

BTW the instructions on the Bundler page ( https://www.chiliproject.org/projects/chiliproject/wiki/Bundler ) show this:

bundle install --without=sqlite postgres rmagick

and I expect it should be either

bundle install --without="sqlite postgres rmagick"

or

bundle install --without=sqlite --without=postgres --without=rmagick

Now I could successfully run: "rake generate_session_store"
and populate the database: "RAILS_ENV=production rake db:migrate"

The rest of the instructions for file permissions were completed.

Although I was able to start Webrick http://<ipaddress>:3000/ did not work

My virtual host file has as document root:

/home/<user>/domains/<domain>/public_html

Following some instructions for Redmine on ServerFault I tried different
symlinks e.g.

ln -s /home/<user>/domains/<domain>/chiliproject /home/<user>/domains/<domain>/public_html

ln -s /home/<user>/domains/<domain>/chiliproject/public /home/<user>/domains/<domain>/public_html

Both of these formats resulted in 403 errors.

Next I copied all the /home/<user>/domains/<domain>/chiliproject files to /public_html which also gave a 403 error.

I also tried changing the document root in the virtual hosts file to /home/<user>/domains/<domain>/chiliproject

So that is where I am at. Everything seems to be installed as described in the installation guide but I cannot access the site.

What am I missing?

Cheers,
Noel


Replies (1)

RE: Insallation gives 403 Error for ChiliProject 2.0.0 - Added by Noel Springer at 2011-07-24 12:48 pm

OK to answer my own question, what I was missing was the Virtual Hosts config.

I had already installed passenger following the instructions from http://www.modrails.com/install.html

Actually when restarting apache after this I had a warning that passenger was already loaded.
The final instructions required adding three lines to the Apache config file, on Debian at /etc/apache2/apache2.conf

LoadModule passenger_module /var/lib/gems/1.8/gems/passenger-3.0.7/ext/apache2/mod_passenger.so
PassengerRoot /var/lib/gems/1.8/gems/passenger-3.0.7
PassengerRuby /usr/bin/ruby1.8

I had already installed libapache2-mod-passenger using aptitude. To solve this I disabled the Apache module
a2dismod passenger and retained the three lines above in the apache2.conf file and restarted Apache.

My final Virtual Hosts file looks something like this (abbreviated).

<VirtualHost MYIP:80>
ServerName chiliproject.example.com
DocumentRoot /PATH/TO/chiliproject/public
ErrorLog /var/log/virtualmin/chiliproject.example.com_error_log
CustomLog /var/log/virtualmin/chiliproject.example.com_access_log combined
<Directory /PATH/TO/chiliproject/public>
allow from all Options -MultiViews
</Directory>
RailsEnv production
</VirtualHost>

So the DocumentRoot was changed from the regular Apache public_html to the ChiliProject public directory and RailsEnv production was added outside the Directory tags.

Further information on the Virtual Hosts deployment is here: http://www.modrails.com/documentation/Users%20guide%20Apache.html#_deploying_a_ruby_on_rails_application

Coming from a PHP Drupal background, there seemed to be more to getting this up and running. One of the questions was, "Where are the code files stored?"
In a regular Drupal installation they are inside the website's document root i.e. public_html on my set up. Perhaps some notes on that in the installation guide would be helpful.

Well looking forward now to further exploring ChiliProject.

Cheers,
Noel

(1-1/1)