incubator-bloodhound-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Branko ─îibej <br...@wandisco.com>
Subject Re: [BEP-0003] Product-specific configuration
Date Fri, 16 Nov 2012 04:11:43 GMT
On 16.11.2012 04:58, Olemis Lang wrote:
> On 11/15/12, Apache Bloodhound <bloodhound-dev@incubator.apache.org> wrote:
>> Page "Proposals/BEP-0003" was changed by olemis
>> Diff URL:
>> <https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0003?action=diff&version=8>
>> Revision 8
>> Comment: [BEP-0003] Product-specific settings (refs #115) and corollaries
>> mentioned by jure in [/wiki/Proposals/BEP-0003?version=5 version 5]
>> Changes:
>> -------8<------8<------8<------8<------8<------8<------8<------8<--------
>> Index: Proposals/BEP-0003
>>
> [...]
>
> In a few words  this change provides a solution for most requirements
> specified by jure in version 5 , as all these tasks are accomplished
> by editing trac.ini . It is based on product environments construct .
>
> If you have any comments about this , please reply this e-mail message
>

It strikes me that this multi-environment proposal makes it relatively
easy to set up completely separate products with their own configuration
(and even their own set of plugins), but ... where do you put common
defaults? Also, managing a zillion .ini files seems like a huge pain,
especially with regards to transaction isolation, data protection
(backup/restore) and replication (e.g., export/import).

I'd be less nervous about the idea if the .ini files could be mapped
into the database.

-- Brane

-- 
Branko ─îibej
Director of Subversion | WANdisco | www.wandisco.com


Mime
View raw message