wohali opened a new issue #593: Allow bind address of 127.0.0.1 in 
_cluster_setup for single node
URL: https://github.com/apache/couchdb/issues/593
 
 
   ## Expected Behavior
   A user should be able to configure a single node CouchDB installation to 
bind to `127.0.0.1` through the Fauxton Setup wizard or via the 
`/_cluster_setup` endpoint.
   
   ## Current Behavior
   Right now, if you use Fauxton to configure a single node CouchDB 
installation, you are forced to set a bind address other than `127.0.0.1`. The 
same is true for the `/_cluster_setup` endpoint.
   
   While this makes sense for configuring an actual cluster, it does not for a 
single node setup.
   
   ## Possible Solutions
   I see two ways to solve this problem:
   
   1. Change Fauxton's wizard for single node setup to directly access the 
`/_node/couchdb@localhost/_config` (substituting the correct node name as 
queried via `/_membership`) endpoint to alter the admin user, bind address and 
port as desired.
   
   2. Improve the `/_cluster_setup` endpoint to accept a new `"action": 
"enable_single_node"` that tolerates binding to `127.0.0.1`. This would have to 
be paired with changing the validation function in Fauxton to accept that bind 
address when in the single node workflow.
   
   I have a mild preference for 2, but 1 requires less work on the backend, and 
doesn't abuse an endpoint intended for setting up _clusters_ to set up a single 
node as well.
   
   Input from @garrensmith and @janl requested.
   
   ## Steps to Reproduce (for bugs)
   1. Install a post-2.0 CouchDB.
   2. Use Fauxton to navigate to the setup wizard.
   3. Try to set up a single node that stays bound to 127.0.0.1. It will fail.
   4. Alternately, use the `/_cluster_setup` end point to do the same thing. It 
also fails.
   
   ## Context
   Real world users very often expect to have a single node CouchDB 
installation bound to localhost only.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to