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.

FAQ

Version 9 (Felix Schäfer, 2015-01-15 11:13 am)

1 1
h1. Frequently asked questions
2 1
3 4 Felix Schäfer
{{>toc}}
4 2 Felix Schäfer
5 2 Felix Schäfer
h2. Why shall I use ChiliProject and not Redmine?
6 2 Felix Schäfer
7 3 Felix Schäfer
ChiliProject is a fork of the "Redmine":http://www.redmine.org project. One of the [[Why Fork|main reasons for forking]] was to gain stronger growth and speed in development by opening the process of contribution to a larger community. We believe that this will gain trust in the community and in the product. That is why we think that you can trust in this project, too.
8 2 Felix Schäfer
9 1
h2. Is ChiliProject OpenSource?
10 1
11 1
Yes, it is provided under the "GNU General Public License, version 2":http://www.gnu.org/licenses/gpl-2.0.html.
12 4 Felix Schäfer
13 8 Felix Schäfer
h2. When will Rails 3 be supported?
14 8 Felix Schäfer
15 8 Felix Schäfer
Rails 3 rewrote how Rails Engines work and are not fully backwards compatible. Since Engines are used by ChiliProject for our plugins, we cannot upgrade to Rails 3 until:
16 8 Felix Schäfer
17 8 Felix Schäfer
* A major ChiliProject release, due to breaking backwards compatibility
18 8 Felix Schäfer
* Rails 3 Engines are completed. Rumors say that will be with Rails 3.1
19 8 Felix Schäfer
* A migration and upgrade path for existing ChiliProject plugins is released
20 8 Felix Schäfer
21 4 Felix Schäfer
h2. What is Bluemine?
22 4 Felix Schäfer
23 4 Felix Schäfer
Bluemine was the code name for ChiliProject before we had an actual name.  It is based on the Ruby's community fascination with colors (RedCloth, BlueCloth).
24 5 Felix Schäfer
25 5 Felix Schäfer
h2. What is the proper name for ChiliProject?
26 5 Felix Schäfer
27 5 Felix Schäfer
The proper name is ChiliProject, as "CamelCase":http://en.wikipedia.org/wiki/CamelCase.  chiliproject is okay too when it's referring to "code" things like a filesystem path (e.g. install to @/var/chiliproject@) or package (e.g. @apt-get install chiliproject@).
28 5 Felix Schäfer
29 5 Felix Schäfer
Chili Project, chili-project, and chiliProject are not the correct spelling.
30 6 Felix Schäfer
31 6 Felix Schäfer
{{html_comment(TODO: Compatibility to Redmine?)}}
32 7 Felix Schäfer
{{html_comment(TODO: Where's the error trace from a 500 error, should probably be on a separate FAQ though)}}
33 9 Felix Schäfer
34 9 Felix Schäfer
h2. How come I have to visit the repository module before I see any changes?
35 9 Felix Schäfer
36 9 Felix Schäfer
ChiliProject needs to load the repository data into the database before it can be used. This happens when visiting the Repository module by default but you can also schedule a cronjob to load the data on a regular schedule.
37 9 Felix Schäfer
38 9 Felix Schäfer
<pre>
39 9 Felix Schäfer
rake redmine:fetch_changesets RAILS_ENV=production
40 9 Felix Schäfer
</pre>
41 9 Felix Schäfer
42 9 Felix Schäfer
p(smallinfo). On Git, Mercurial, and other repositories that have a local copy need to have the changes sent to the repository first. e.g. @git push@ for git.