couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Shorin (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1744) Make the config file optional
Date Sun, 07 Jul 2013 00:05:48 GMT


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,

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:
>             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
> 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:

View raw message