If someone can explain how we can start in admin party mode, where couchdb is only listening on the loopback interface, while simultaneously allowing a cluster to be connected, I would be much obliged.
B. On 24 Sep 2014, at 12:58, Andy Wenk <[email protected]> wrote: > On 24 September 2014 13:31, Alexander Shorin <[email protected]> wrote: > >> On Wed, Sep 24, 2014 at 3:23 PM, Dirkjan Ochtman <[email protected]> >> wrote: >>> On Wed, Sep 24, 2014 at 12:35 PM, Jan Lehnardt <[email protected]> wrote: >>>> That’s it so far, what do you think? :) >>> >>> It sucks that/if Admin Party has to go. Firewalls or only listening on >>> 127.0.0.1 are a perfectly fine solution, IMO. >>> >>> I would really like to be able to do simple forms of setup from the >>> command-line, rather than having to go through a browser. For the >>> simple case of setting up a single-node cluster, realistically I'm >>> going to issue /etc/init.d/couchdb start and then want to get started. >>> If I'm not required to context-switch to browser for any required >>> setup steps, that would be a win IMO. >> >> and +1 on this. I would really miss that feature too. >> >> -- >> ,,,^..^,,, >> > > just asked the same question on IRC like Dirkjan asked here. So also my +1 > on the cli setup AND > > +1 for all this Jan. Really appreciated :) > > Cheers > > Andy > > -- > Andy Wenk > Hamburg - Germany > RockIt! > > GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588 > > https://people.apache.org/keys/committer/andywenk.asc
