Better handling of missing configuration files

Open prandla opened this issue 6 months ago • 1 comments

Current behavior when cms can't find any config file: (and normally the DEBUG lines aren't even shown.)

I feel like we should just throw an error immediately when no config file can be found. I guess for most config options, using the built-in defaults can be useful in some cases, but I really don't think it makes sense for the DB connection string to be defaulted.

I think failure to load an explicitly-specified CMS_CONFIG variable should also be an error.

cmsranking also has a similar feature: cmsRankingWebServer[136225]: 2025-06-12 20:33:24.336 WRN No config file found, using hardcoded defaults.

Jun 15 '25 13:06 prandla

I agree that failing to load a configuration file should just hard-error. I can't imagine usecases in which you might want to continue with defaults...

Jun 15 '25 21:06 veluca93

Fixed by #1426.

Jul 01 '25 13:07 prandla