couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Shorin (JIRA)" <>
Subject [jira] [Closed] (COUCHDB-1086) Improve config file write-back behavior.
Date Fri, 31 Oct 2014 15:52:35 GMT


Alexander Shorin closed COUCHDB-1086.
    Resolution: Not a Problem

CouchDB writes config changes into the last file in the chain. The chain by default is looks
like  {{-a /etc/couchdb/default.ini -a /etc/couchdb/default.d/* -a /etc/couchdb/local.ini
-a /etc/couchdb/local.d/*}}. So if you don't see config changes in local.ini, you need to
check any ini files inside local.d/ directory.

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

View raw message