[
https://issues.apache.org/jira/browse/COUCHDB-2623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15457543#comment-15457543
]
Joan Touzet commented on COUCHDB-2623:
--------------------------------------
I put together a little grep+python script that you can run across the entire
code base to find all config:get calls and print them in a useful fashion. Run
using:
{code}
$ grep -ri config:get * | grep .erl > config.txt
$ python parse.py config.txt > out.txt
{code}
Here's the [python
script|https://gist.github.com/wohali/b1b393427d5554bd0dcbf5cc1e6c38bb]. The
output against the RC4 code tree is
[here|https://gist.github.com/wohali/3ccfe629022289d8b6f56b744dfda679]. I'm now
going through this list to see that everything is documented in our sample
default.ini/local.ini file.
I don't intend to port any of this documentation into the documentation tree at
this point; a well documented sample .ini file will suffice.
> Validate default.ini / local.ini config options
> -----------------------------------------------
>
> Key: COUCHDB-2623
> URL: https://issues.apache.org/jira/browse/COUCHDB-2623
> Project: CouchDB
> Issue Type: Task
> Reporter: Alexander Shorin
> Priority: Blocker
> Labels: todo
> Fix For: 2.0.0
>
>
> We need to double check our configs to ensure that there are no outdated
> options there and all the present ones are actual to their defaults. For
> instance:
> {code}
> [stats]
> ; rate is in milliseconds
> rate = 1000
> ; sample intervals are in seconds
> samples = [0, 60, 300, 900]
> {code}
> Is not actual anymore since we'd change the stats app, but those might expose
> new ones.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
