You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Michael Wiederhold (JIRA)" <ji...@apache.org> on 2011/03/10 01:45:59 UTC
[jira] Created: (COUCHDB-1086) Changing bind address in futon does
record the new address correctly in config files
Changing bind address in futon does record the new address correctly in config files
------------------------------------------------------------------------------------
Key: COUCHDB-1086
URL: https://issues.apache.org/jira/browse/COUCHDB-1086
Project: CouchDB
Issue Type: Bug
Components: Futon
Affects Versions: 1.0.2
Environment: Ubuntu 10.04
Reporter: Michael Wiederhold
Priority: Critical
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
[jira] Commented: (COUCHDB-1086) Improve config file write-back
behavior.
Posted by "Paul Joseph Davis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13004953#comment-13004953 ]
Paul Joseph Davis commented on COUCHDB-1086:
--------------------------------------------
Isn't that what $PREFIX/etc/couchdb/default.d/ is for?
> 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
[jira] Commented: (COUCHDB-1086) Improve config file write-back
behavior.
Posted by "Chris Anderson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13004949#comment-13004949 ]
Chris Anderson commented on COUCHDB-1086:
-----------------------------------------
I think we should do what we can to make plugins smooth. Maybe we could have a COUCH_PLUGIN_INIS environment variable that is inserted between default.ini and local.ini
> 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
[jira] [Commented] (COUCHDB-1086) Improve config file write-back
behavior.
Posted by "Jan Lehnardt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020670#comment-13020670 ]
Jan Lehnardt commented on COUCHDB-1086:
---------------------------------------
local.ini should take precedence.
I'm a bit hazy on the use-case for local.d if we never write back to anything but local.ini. Maybe it was though that plugins could have their own write-back files, but CouchDB doesn't support any of that. Maybe Noah remembers?
Either way, geocouch.ini should go in default.d.
> 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
[jira] Commented: (COUCHDB-1086) Changing bind address in futon
does record the new address correctly in config files
Posted by "Paul Joseph Davis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13004912#comment-13004912 ]
Paul Joseph Davis commented on COUCHDB-1086:
--------------------------------------------
Couch will always write to the last confit file spacified. There's no code that treats local.ini any differently than any other config file, it's merely convention. I'd close this outright as won't fix but I'll wait and see if anyone has a good idea on how to do this differently. For instance there were previous suggestions on writing back to the last file where the setting was specified, or by specifying the file to write to on the command line. Well I may have just thought of that last one. Anyway, yeah, not a bug but maybe there's an enhancement here.
> Changing bind address in futon does record the new address correctly in config files
> ------------------------------------------------------------------------------------
>
> Key: COUCHDB-1086
> URL: https://issues.apache.org/jira/browse/COUCHDB-1086
> Project: CouchDB
> Issue Type: Bug
> Components: Futon
> Affects Versions: 1.0.2
> Environment: Ubuntu 10.04
> Reporter: Michael Wiederhold
> Priority: Critical
>
> 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
[jira] Updated: (COUCHDB-1086) Improve config file write-back
behavior.
Posted by "Paul Joseph Davis (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (COUCHDB-1086) Improve config file write-back
behavior.
Posted by "Michael Wiederhold (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13004954#comment-13004954 ]
Michael Wiederhold commented on COUCHDB-1086:
---------------------------------------------
I installed on Ubuntu 10.04 with the 64bit download from couchone.com. I was also somewhat surprised that it had geocouch in it. Either was local.ini is not the top level config file. (Also the geocouch config is contained in etc/couchdb/local.d/)
> 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
[jira] Commented: (COUCHDB-1086) Improve config file write-back
behavior.
Posted by "Paul Joseph Davis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13004937#comment-13004937 ]
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: 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
[jira] Commented: (COUCHDB-1086) Improve config file write-back
behavior.
Posted by "Michael Wiederhold (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13004923#comment-13004923 ]
Michael Wiederhold commented on COUCHDB-1086:
---------------------------------------------
If it is the case that writing to the last config file specified is always the correct behavior then having a local.ini files seems somewhat useless since there wouldn't be anything in it unless the user manually wrote to it.
Agreed on the lower priority.
> 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
[jira] Updated: (COUCHDB-1086) Changing bind address in futon does
record the new address correctly in config files
Posted by "Paul Joseph Davis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Joseph Davis updated COUCHDB-1086:
---------------------------------------
Priority: Minor (was: Critical)
Affects Version/s: (was: 1.0.2)
Skill Level: New Contributors Level (Easy) (was: Dont Know)
Issue Type: Improvement (was: Bug)
Marked as lower priority improvement.
> Changing bind address in futon does record the new address correctly in config files
> ------------------------------------------------------------------------------------
>
> 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
[jira] Commented: (COUCHDB-1086) Improve config file write-back
behavior.
Posted by "Volker Mische (JIRA)" <ji...@apache.org>.
[ 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