Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Date: Thu, 10 Mar 2011 01:09:59 +0000 (UTC)
From: "Paul Joseph Davis (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Message-ID: 
 <1841869466.9784.1299719399478.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <335384205.9685.1299717959452.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Updated: (COUCHDB-1086) Improve config file write-back
 behavior.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/COUCHDB-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Joseph Davis updated COUCHDB-1086:
---------------------------------------

    Summary: Improve config file write-back behavior.   (was: Changing bind address in futon does record the new address correctly in config files)

> 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