add a wizard for setting up a cluster

[robertkowalski]

how to test:

set the port in exports.couch to a node that will handle the
setup (the "setup-node"):

exports.couch = 'http://localhost:15984/';

if you change the port of the setup node during setup the wizard will
lose the connection and can't finish.

(this will change in a proper release where fauxton is running on each node)

how to run couch:

rm -rf dev/lib/ && rm -rf dev/logs/ && /dev/run --with-admin-party-please --no-join

deletes your dbs, the --no-join spawns three nodes that are not joined into a cluster

[robertkowalski]

note: you need to run configure & make before testing, as it requires the latest version of https://github.com/apache/couchdb-setup

[robertkowalski]

scenarios:

single node setup (set port in form to 15984):
rm -rf dev/lib/ && rm -rf dev/logs/ && /dev/run --with-admin-party-please --no-join -n1
rm -rf dev/lib/ && rm -rf dev/logs/ && /dev/run --admin=tester:testerpass --no-join -n1


three node setup (set port in form for main node to 15984 and add 25984, 35984):
rm -rf dev/lib/ && rm -rf dev/logs/ && /dev/run --with-admin-party-please --no-join
rm -rf dev/lib/ && rm -rf dev/logs/ && /dev/run --admin=tester:testerpass --no-join

[michellephung]

this is working ok.

a little confusing what ports are acceptable, but not a blocker
+1 because it is working.

one small thing:

I think this is supposed to say something other than 'undefined'.

[robertkowalski]

I think this is supposed to say something other than 'undefined'.

it goes away if you restart grunt after switching the branch, because the build system has to bake the string into the dashboard.

[robertkowalski]

merged!