Mailing-List: contact bloodhound-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: bloodhound-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of olemis@gmail.com designates
 209.85.223.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <50F038FE.6000006@digiverse.si>
References: <053.0e57377525de9e84b59ecf4d36bdc79a@incubator.apache.org>
	<50F038FE.6000006@digiverse.si>
Date: Fri, 11 Jan 2013 15:27:59 -0500
Message-ID: 
 <CAGMZAuM-X6EX45YDb-u0NPJhey=Cw0jFv8zxd5A498q6dhGmGA@mail.gmail.com>
Subject: Re: [Apache Bloodhound] #323: Add support for custom hooks
 configurable through trac.ini
From: Olemis Lang <olemis@gmail.com>
To: bloodhound-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On 1/11/13, Jure Zitnik <jure@digiverse.si> wrote:
>
[...]
>
> So I was playing with an idea to introduce global.ini (or boot.ini or
> something like that) that would be located on a well-known location in
> the installation tree (trac.env_parent_dir for example) and would hold
> global (=common for all environments) settings (custom hooks for
> starters). The question is where this configuration is supposed to be
> loaded/processed. trac/__init__.py would be one place but I'm not sure
> that's the right one :)
>

IMO there's no reason to spend some time developing something new for
this to happen . The reason is *not* that your reasoning is not
correct . The fact is that this (configuration inheritance) has been
already there since a long time . If you have one such file e.g.
global.ini and add the following lines in trac.ini

{{{
#!ini

[inherit]
file = /path/to/global.ini

}}}

then trac.ini will inherit all the settings specified in there .

So IMO , instead of modifying the source code to introduce such global
configuration files , I'd rather suggest to setup this at deployment
time e.g. in installer script .

PS: configuration inheritance even works for product environments ...
mainly in two (complementary) ways :

  1. if there's a value for [inherit] file option stored
      product config table (i.e. in the database) then
      it will work just like explained above for ini files .
      Relative paths are resolved relative to
      /path/to/env/conf sub-folder
  2. `parents` arg in multiproduct.config.Configuration.__init__

-- 
Regards,

Olemis.

Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/

Featured article: