GitHub user robertkowalski opened a pull request:
https://github.com/apache/couchdb-fauxton/pull/360
Cluster configuration fixes for 2.0
In CouchDB 2.0 we don't have `_config` on the clustered interface. As
user/admin management also uses _config, also hide it on a cluster.
We still support it on the backdoor ports.
closes COUCHDB-2601 COUCHDB-2599 COUCHDB-2390
COUCHDB-2390
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/robertkowalski/couchdb-fauxton
2601-2390-config-backdoor
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/couchdb-fauxton/pull/360.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #360
----
commit b376bcaee66a605e9bb7bfc179fa797f8288f0b3
Author: Robert Kowalski <[email protected]>
Date: 2015-04-03T20:18:13Z
test: remove confirmdialog
when running the testsuite in the browser tests were stopped unti
confirming with `OK`
commit b026a0d85fd9e1251954ce588f7329318312d595
Author: Robert Kowalski <[email protected]>
Date: 2015-04-02T19:52:23Z
config: just show config where it is available
In CouchDB 2.0 we don't have `_config` on the clustered interface.
We still support it on the backdoor ports.
closes COUCHDB-2601
COUCHDB-2390
commit 28f6a12a103fdf98b2719ccd0eb4ae96e1059279
Author: Robert Kowalski <[email protected]>
Date: 2015-04-04T00:02:41Z
login: remove dead code
commit a2e499bc979c6eb46e6ec2cac9bb086ce5c5a810
Author: Robert Kowalski <[email protected]>
Date: 2015-04-04T00:05:09Z
move usermanagement which uses `_config` to config
commit 9340260d00caf1256d25e83d846b6dadca43f857
Author: Robert Kowalski <[email protected]>
Date: 2015-04-04T12:46:34Z
admin: do not show up on a cluster
`_config` is not available on a cluster, so don't offer to alter
it for creating admins, changing passwords and fixing the party
mode.
closes COUCHDB-2601 COUCHDB-2599 COUCHDB-2390
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
