couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Lehnardt <...@apache.org>
Subject Re: Configuration Load Order
Date Mon, 15 Aug 2011 17:32:10 GMT

On Jul 19, 2011, at 5:28 PM, Noah Slater wrote:

> 
> On 19 Jul 2011, at 09:22, Matt Goodall wrote:
> 
>> This makes sense to me. Personally, I don't think a
>> generated.ini/generated.d pair is needed - just a single generated.ini would
>> do.
>> 
>> As well as ensuring changes are written to the last .ini file in the
>> configuration chain a generated.ini would act very nicely as a per-instance
>> configuration for when multiple CouchDB instances are run from the same,
>> read-only installation, i.e.
>> 
>>   default.ini/default.d  --  CouchDB default config, system-wide (R)
>>   local.ini/local.d  --  local sysadmin's config, system-wide (R)
>>   generated.ini  --  per-instance config (RW)
>> 
>> As such, I would suggest naming generated.ini something more like
>> instance.ini.
> 
> I am +1 on all of this.

This doesn't solve the problem that spawned this discussion:

1. Write admin = password to local.ini
2. Restart CouchDB
3. Hash gets persisted to generated.ini
4. Plain text password remains in local.ini

Cheers
Jan
-- 



Mime
View raw message