[
https://issues.apache.org/jira/browse/COUCHDB-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14636796#comment-14636796
]
ASF subversion and git services commented on COUCHDB-2390:
----------------------------------------------------------
Commit 5de1fe6682fc5a9dee44022498357febd73c3600 in couchdb-fauxton's branch
refs/heads/master from [~robertkowalski]
[ https://git-wip-us.apache.org/repos/asf?p=couchdb-fauxton.git;h=5de1fe6 ]
Just enable config for a "cluster-of-one"
Warn users if they run multi node setups.
Testing instructions for single node setups, given you usually run
a cluster of three nodes:
1. stop couchdb, connect fauxton to a single node, change
```
exports.couch = 'http://localhost:15984/';
```
in `tasks/helper.js`
2. get rid of `dev/lib/` in the couchdb folder, so the cluster does
not know about the other nodes any more, caution: you will lose
your current dbs.
3. boot couchdb with one node:
```
./dev/run --with-admin-party-please -n1
```
4. PROFIT!
COUCHDB-2601 COUCHDB-2599 COUCHDB-2390
PR: #480
PR-URL: https://github.com/apache/couchdb-fauxton/pull/480
Reviewed-By: garren smith <[email protected]>
> Fauxton config, admin sections considered dangerous in 2.0
> ----------------------------------------------------------
>
> Key: COUCHDB-2390
> URL: https://issues.apache.org/jira/browse/COUCHDB-2390
> Project: CouchDB
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: BigCouch, Fauxton
> Reporter: Joan Touzet
> Assignee: Ben Keen
> Priority: Blocker
> Fix For: 2.0.0
>
>
> In Fauxton today, there is are 2 sections to edit config-file settings and to
> create new admins. Neither of these sections will work as intended in a
> clustered setup.
> Any Fauxton session will necessarily be speaking to a single machine. The
> config APIs and admin user info as exposed will only add that information to
> a single node's .ini file.
> We should hide these features in Fauxton for now (short-term fix) and correct
> the config /admin creation APIs to work correctly in a clustered setup
> (medium-term fix).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
