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.

configuration.yml.example is broken (Bug #1144)

Added by Gordon Anderson at 2012-09-13 04:48 pm. Updated at 2012-09-15 04:02 pm.

Status:Closed Start date:2012-09-13
Priority:Normal Due date:
Assignee:Holger Just % Done:


Target version:3.4.0
Remote issue URL: Affected version:2.7.3


I ran into an issue where I could not get mail configuration to work, even though the file was there. After much reading of Redmine bug reports, I eventually found the culprit. There are 2 sections marked 'production' in the YAML file, and the second one, which is empty, overwrites the first. I found this issue with 2.7.3, the same issue does not occur with 2.6.0, and I was using an identical configuration.yml file.

Suggested fix is to remove the empty production: section

Associated revisions

Revision 003fc93b
Added by Holger Just at 2012-09-14 10:27 pm

Make the commented configuration.yml.example more approachable #1144


Updated by Holger Just at 2012-09-13 07:00 pm

If you look closely, you will notice that on the start of the file, the production is commented. This might indeed a bit confusing but we have only one actually defined production environment in this file.

To mitigate this, I'd propose to remove the email examples and to point users to Configuration File and especially Email Delivery. This would leave the default section fully documented with all available options. And would still allow people to override specific options for some environments.

Updated by Gordon Anderson at 2012-09-14 07:46 pm

hi Holger

Re-reading I realize that you are correct, and I had realised this after I posted it. I guess the confusing thing for me was that the same configuration used to work, and it was only after googling error messages that I discovered the cause of the apparently missing email configuration. Your suggestion does seem sensible.

Cheers, and thanks for the feedback :)


Updated by Holger Just at 2012-09-14 08:29 pm

A default configuration.yml in this format is probably a good idea.

  • Assignee set to Holger Just

Updated by Holger Just at 2012-09-14 10:31 pm

In 003fc93 I pushed a much more approachable and better commented version of the configuration.yml.example.

  • Status changed from Open to Closed
  • Target version set to 3.4.0

Updated by Gordon Anderson at 2012-09-15 04:02 pm

Many thanks, hopefully it will save someone time in future :)

Also available in: Atom PDF