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.

Chef Cookbook



The cookbook was created with focus on Debian/Ubuntu but should also work on RHEL and SUSE like systems. In fact, it should be easy to support any Unix/Linux system which is able to meet the basic requirements of both ChiliProject and Chef.

Due to some bugs in earlier version of Chef, we require at least Chef 10.12.0 on the server. These issues are:

  • When performing sub-path deployments, i.e., setting a base_uri to a URL with a path component, a bug present in Chef <= 0.10.10 prevents us from creating the required symlinks for the Apache+Passenger config. This is fixed with in CHEF-3110. Thus you need at least Chef 10.12.0 when all of these conditions apply:
    • You are using sub-path deployments
    • You are using the chiliproject::apache2 cookbook for setting up Passenger
  • For similar reasons, you need Chef >= 10.12.0 when installing plugins.

Basic Usage

One of the main goals was to allow multiple ChiliProject instances on the same server. To facilitate this, we use data bags to configure the instances.



To uninstall a ChiliProject instance

  • delete /opt/chiliproject/[instance name]
  • delete /opt/chiliproject/shared/[instance name] - this will delete all user-uploaded files including repositories.
  • remove the user chili_[instance name]
  • remove the groups chili_[instance_name], chili_[instance_name]_repos
  • remove the database chili_[instance_name]
  • remove the Apache virtual host in /etc/apache2/sites-enabled/chili_[instance name].conf and /etc/apache2/sites-available/chili_[instance name].conf

Then remove the data bag item for the instance: chiliproject/[instance name].json.