Project

General

Profile

Actions

Defect #9748

closed

Error about configuration.yml validness should mention file path

Added by Mark P over 12 years ago. Updated over 12 years ago.

Status:
Closed
Priority:
Normal
Category:
-
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed
Affected version:

Description

We've been using Redmine since the .7.x days, and done several upgrades to stay current, and this is the first time I have had any issues. When I upgraded from 1.0.1 to 1.2.2 in my non-production instance, I get the following when I ran rake --trace db:migrate RAILS_ENV=development:

syntax error on line 150, col 0: `production:'

After grepping around a bit, we found that line in the configuration.yml file. Just a stab in the dark, we commented that out, and tried again. Then we got this one:

syntax error on line 154, col 0: `development:'

Which points to the development entry on line 154 of the configuration.yml file. So, I commented that out too, and ran the rake again with no issues. My non-production instance is now up and running fine.

My question is related to the purpose of those lines as they come shipped in the configuration.yml file. I have to assume they are non commented for a reason. My having to comment them out makes me think something else is incorrect.

The files comments say this:

# specific configuration options for production environment
# that overrides the default ones

Both the production and development lines are enabled, leading me to believe that the file wants to override default values, but where are those default values coming from, and what are they? If I comment both prod and dev out, then are the configuration.yml file settings being used or not? I want to make sure that if I leave them commented out, then I won't be plagued with some continual issues in the future.

Thank you in advance for your help, and as always, nice job on the Redmine project.


Related issues

Related to Redmine - Defect #35421: Unhandled exception when a YAML syntax error is detected in configuration.ymlClosedGo MAEDA

Actions
Actions

Also available in: Atom PDF