couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Joseph Davis (JIRA)" <>
Subject [jira] Commented: (COUCHDB-1086) Improve config file write-back behavior.
Date Thu, 10 Mar 2011 01:47:59 GMT


Paul Joseph Davis commented on COUCHDB-1086:

Not sure what you mean. By default local.ini is the last config file specified and by default
takes all config writes from Futon. I'm not sure what version of CouchDB you're running, but
seeing as you mentioned GeoCouch its not an official release so I can't comment on what's
going on there.

But local.ini is by default blank. The point of its existence is to be the place where config
writes go from Futon or for when users want to override the default.ini config. This way when
users upgrade couch their local.ini is not overwritten so their edits stick around.

> Improve config file write-back behavior. 
> -----------------------------------------
>                 Key: COUCHDB-1086
>                 URL:
>             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 so I can access
couch remotely.
> 2) In futon I change the bind address to 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
> 4) I then go into local.ini and there is nothing except for comments.
> 5) I restart the server and it binds to 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:

View raw message