On 7/15/14, Gary Martin <[email protected]> wrote: > On 15/07/14 00:25, Olemis Lang wrote: >> 2. write product configuration in a ini file (as usual) and execute >> trac-admin /path/to/env product admin PREFIX config set trac inherit > > This would be an interesting option though potentially confusing. I'm > not sure it actually works but my attempts could have been flawed. > > So, presumably you meant: > > trac-admin /path/to/env product admin PREFIX config set inherit file > /path/to/PREFIX.ini >
Yes , sorry , my mistake when copying / pasting . > or something similar. If we assume that the product config is close to a > full implementation of the global config then we would expect that to > allow us to set defaults in the file. There are a few interesting > problems with this. First of all, effectively this would override > settings in the base.ini that the global trac.ini inherits from. True . It's necessary to specify a comma delimited list of file paths , including base.ini and user-defined .ini file . > Secondly, there is a potential for confusion when admins attempt to set > options in the product's config file but the settings are ignored in > preference for using the db settings. > Yes , that's the expected behavior . DB settings will override inherited settings e.g. ini file . [...] -- Regards, Olemis - @olemislc Apache(tm) Bloodhound contributor http://issues.apache.org/bloodhound http://blood-hound.net Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article:
