[
https://issues.apache.org/jira/browse/COUCHDB-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13004971#comment-13004971
]
Volker Mische commented on COUCHDB-1086:
----------------------------------------
To make things a bit clearer. Michael was using CouchDB that had a config file
in local.d (geocouch.ini). When he changed a setting, it was added to that
geocouch.ini.
Thanks Paul for pointing out default.d, I don't know why I wasn't aware of it
before, but I only knew local.d. The default geocouch.ini should go into
default.d.
Back to the original bug report. The basic question is, whether the files in
local.d should overwrite local.ini or not. If we would change the priority of
local.ini to be more important than local.d, then the changes would always end
up in local.ini. Though I'm not sure if that's a good idea.
> Improve config file write-back behavior.
> -----------------------------------------
>
> Key: COUCHDB-1086
> URL: https://issues.apache.org/jira/browse/COUCHDB-1086
> Project: CouchDB
> Issue Type: Improvement
> Components: Futon
> Environment: Ubuntu 10.04
> Reporter: Michael Wiederhold
> Priority: Minor
>
> 1) I install couchdb and change the bind address in default.ini to 0.0.0.0 so
> I can access couch remotely.
> 2) In futon I change the bind address to 127.0.0.1 and then refresh the web
> page an the web ui disappears.
> 3) I go back into the config file default.ini and the bind address is still
> 0.0.0.0.
> 4) I then go into local.ini and there is nothing except for comments.
> 5) I restart the server and it binds to 127.0.0.1 and I cannot see futon.
> The issue is that when changing the bind address in futon, futon puts the new
> address in the config file with the highest priority which is in this case
> the geocouch config file, but the proper place to put the new bind address is
> in local.ini.
> I marked this as critical because I can see it affecting a decent amount of
> users. Should be a quick fix.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
