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 »

How do you manage your Chiliproject install's codebase under git?

Added by Pauli Price at 2011-12-20 10:40 pm

So - how do you manage your Chiliproject codebase? In particular, how do you manage the vendor'ed stuff that's not part of the stock Chiliproject install? What's your workflow when upgrading plugins, versus upgrading the core Chiliproject codebase?

I'm running Chiliproject 1.3 with git integrated for code repository, plus a few Redmine plugins, including DMSF. I'd like to create a repository for our installation and deploy from it, before upgrading to 2.5+. I'm looking for inspiration and maybe guidance on establishing a Git workflow in maintaining this installation.


Replies (1)

RE: How do you manage your Chiliproject install's codebase under git? - Added by Felix Schäfer at 2011-12-21 08:06 am

We manage the plugins we use as submodules, other than that, some smallish ruby scripts, but no big magic.

(1-1/1)