couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1744) Make the config file optional
Date Mon, 16 Dec 2013 20:04:07 GMT


ASF subversion and git services commented on COUCHDB-1744:

Commit 1c344a9669f6b3b6bafeac82ddc29a52d3eccf18 in branch refs/heads/1744-single-config-file
from [~kxepal]
[;h=1c344a9 ]

Ship single full document default config file.

The default.ini becomes really solid default config file with full set of
options with short documentation and default values. The big warning alerts you,
that any changes made in default.ini might be overwritten and suggests you
to use local.ini for any modifications instead.

The local.ini is removed and doesn't ships with new CouchDB installations.
This also resolves issue when after CouchDB upgrade package manager asks users
to merge their local.ini with shipped one. However, when CouchDB starts it
checks for local.ini existence and will create it if missed to keep there all
config options modifications.


> 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 was sent by Atlassian JIRA

View raw message