couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexander Shorin <kxe...@gmail.com>
Subject Re: [jira] [Commented] (COUCHDB-1744) Make the config file optional
Date Wed, 10 Jul 2013 18:41:14 GMT
Filippo,

Yes, it's how it's done for any other projects. However, the
default.ini is real functional config file with some explicitly setted
options like path, HTTP resources, internal services and some other
things that a bit different from code defaults to improve user
experience a bit right out of the box.
IMHO, this is awesome feature for CouchDB distributors, since they are
able to prepare their own default.ini (by patches over the original
source) without rick to have conflicts with user's local.ini file.
--
,,,^..^,,,


On Wed, Jul 10, 2013 at 4:24 PM, Filippo Fadda
<filippo.fadda@programmazione.it> wrote:
> IMO, instead of default.ini and local.ini we should have something like couchdb.ini and
couchdb.ini-default or couchdb-default.ini, so you don't need to read the documentation to
understand what they do, because their name are self-explaining.
>
> -Filippo
>
> On Jul 7, 2013, at 2:05 AM, Alexander Shorin (JIRA) wrote:
>
>>
>>    [ https://issues.apache.org/jira/browse/COUCHDB-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13701453#comment-13701453
]
>>
>> Alexander Shorin commented on COUCHDB-1744:
>> -------------------------------------------
>>
>> It doesn't simply to move everything from default.ini to source code.
>>
>> The Problems:
>>
>> 1. The default.ini contains options with values that are been generated on compilation
stage. Obliviously, there is no good way to have portable default value for databases, views
and log locations.
>>
>> 2. The default.ini contains options that are always been updated with CouchDB (vendor/version,
couchdb/util_driver_dir).
>>
>> 3. The default.ini contains explicit definition of active internal services, special
HTTP resources handlers. If they will be moved into the source code, their customization will
be no more explicit.
>>
>> 4. In common practice is to provide some example config file, well documented with
full set of available options while actual config is in separate file which mostly handwritten
or just modified copy-pasted version of the example one.
>>
>> Bonus: If you're configuring CouchDB via HTTP API you actually don't care about what
and how much config files are exists on FS - you have just a single list of options in Futon.
>>
>> Commit about changes nothing in current config system, but makes default.ini as master
config while you still can create your own overlay as local.ini.
>>
>>> Make the config file optional
>>> -----------------------------
>>>
>>>                Key: COUCHDB-1744
>>>                URL: https://issues.apache.org/jira/browse/COUCHDB-1744
>>>            Project: CouchDB
>>>         Issue Type: Improvement
>>>           Reporter: Dave Cottlehuber
>>>             Labels: gsoc, mentor
>>>
>>> 1) move defaults into the code
>>> 2) instead of local/default, ship a fully complete config with all of its lines
commented out
>>> This will make everybody's life simpler.
>>
>> --
>> This message is automatically generated by JIRA.
>> If you think it was sent incorrectly, please contact your JIRA administrators
>> For more information on JIRA, see: http://www.atlassian.com/software/jira
>

Mime
View raw message