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.
Help with CentOS 6 Install
I'm attempting to install ChiliProject on CentOS 6 and would like to do so without installing more than I need to. I plan on using it with git.
I'm sure I can get it running by following some of the different Redmine install instructions and the CentOS 5 instructions on the ChiliProject site, but since they're all a little different, and I hate to just continually install things without good reason, I'd love a little assistance in creating a nice clean install.
My CentOS install is a pretty straightforward LAMP install. Everything is running as it should without issue.My initial process is as follows:
- Added the EPEL repo for yum.
- Cloned the git repo
- installed ruby and rubygems using yum
- installed bundler using gem
- ran bundle install --without=test sqlite postgres
At that point bundle failed on the gem install of json, as it complained of missing header file
mkmf.rb can't find header files for ruby at /usr/lib/ruby/ruby.h
I decided to move ahead anyway and see what would happen. I created a DB, setup the database.yml and configure.yml files.
I then ran
bundle exec rake generate_session_store
But it failed as well (Sorry I don't have that error anymore as I reverted to a previous snapshot of my VM)
So now I'm here trying to get a good sense of what all is required to get a good install up and running without installing 10,000 -devel packages that may or may not be necessary. Once I've got it down, I'll be happy to add to the CentOS install guide to help others in the future.
RE: Help with CentOS 6 Install - Added by Felix Schäfer at 2011-12-09 01:47 pm
I mostly use source distributions (gentoo) or quasi-source package managers (macports, homebrew), so I'm not sure I can give you a definitive list, but I guess the only way to be sure would be to just try to install all the gems, see where it complains and install the necessary packages as needed?
Anyway, the things I can think of off the top of my head that would be necessary are the ruby devel package (needed in any case to compile binary extensions for rubyâ€¦), the mysql-devel stuff (not sure if mysqllib-devel or the equivalent for CentOS would be enough thoughâ€¦) as you seem to lean towards mysql, if you want imagemagick support (IIRC only needed for png export of gantt charts) obviously the imagemagick stuff (you can disable the imagemagick support in the bundle install phase though).
I hope this helps, if not try to grad
khalsa on IRC as he was the one who did the CentOS5 stuff, he's quite busy though so it might be a few minutes/hours before he comes by.
I'm actually in the process of doing this myself. Have a fresh install of CentOS 6.1. I have already gone through the pain of getting Chili project running on a Windows 2008 R2 environment and found the necessary juggling atrocious (more a problem with Ruby than Chili project).
If you get a clean install set before I do please post! Thanks.
RE: Help with CentOS 6 Install - Added by John Peel at 2011-12-11 03:14 pm
I haven't had a chance to work on it since my original post but, am hoping to have time today. I will definitely repost here if/when I get an install up and running that I feel comfortable with.
RE: Help with CentOS 6 Install - Added by Muntek Singh at 2011-12-26 10:06 pm
Was this resolved? I won't be migrating a lot of my stuff to 6.2 until Late January, but am always willing to help in IRC as mentioned.
RE: Help with CentOS 6 Install - Added by John Peel at 2012-01-10 09:36 pm
Thanks for following up. I apologize as I have still been swamped since I initially posted and have not had time to resolve this. It also appears that I need to get more intimate with the inner workings of GIT and make sure I have a proper workflow in place before rolling out any of this. I'm new to this whole version control and project management game, so after diving right in, I have climbed back out and am now wading back in as time permits.