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.

Question about multiple instances.

Added by chili peper at 2012-02-22 02:02 pm

Hello,

is it possible to run multiple instances with separate db's of chiliproject on one server? if so, could you point me to some documenation about it ?

thanks.


Replies (2)

RE: Question about multiple instances. - Added by Kris Lou at 2012-02-22 05:53 pm

I don't see why you can't. Just install to a separate location (e.g. /var/www/chiliproject-2) and change the appropriate database.yml to point to a different backend. Then you'd have to redirect Mongrel/Thin/Passenger to probably listen to a different port than your original installation, and the same for your front end web server. Or at least, that's what I'd have to do with my implementation.

Personally, I'd much rather administer a single installation and build access controls via Roles than maintain several separate environments...

RE: Question about multiple instances. - Added by Felix Schäfer at 2012-02-22 10:01 pm

If you mean "running multiple instances from one codebase", I'd strongly advise against it because not all parts of ChiliProject are "environment-agnostic" (environments is what is used in rails-land to describe different sets of settings of one codebase/app). What you can do though is just make a normal install in as many separate directories as you need instances.

(1-2/2)