Hi, Jan.
Sorry for late response.
On Fri, Jul 3, 2015 at 12:00 AM, Jan Lehnardt j...@apache.org wrote:
Like Robert’s proposal said, for “clusters of one”, we can just show the
config screen.
Good, that will works. I seems missed this moment (:
- Sorry, 2.0 is not friendly for simple
Just a note: anyone actually *upgrading* from 1.6 isn't going to have
anything but a cluster-of-one, so I think that limiting the web UI to
cluster-of-one setups is perfectly fine (nobody is losing capability).
Any cluster-of-N deployment is going to be new by definition, so
having to use a new
Hi Robert,
On Wed, Jul 1, 2015 at 4:14 PM, Robert Kowalski r...@kowalski.gd wrote:
Here are the things I found out or I had to explain:
- the feature is not intended for more than 5, maybe 10 nodes as it is
not feasible for the user and also gets more and more error prone the
more nodes we
I like your proposal. It sounds carefully considered and planned. I
like the idea that the UI communicates in a direct and clear way that
another (maybe external) tooling is necessary as soon as you're dealing
with a cluster.
I believe that not making any compromises (as in we only have to
On Thu, Jul 2, 2015 at 11:31 PM, Jan Lehnardt j...@apache.org wrote:
I really like your attempt to preserve this 1.x-ism for small clusters.
I’m not sure I feel really good about this though, for the same reasons
that Robert K outlined.
I’d be more comfortable in saying 2.0 does not have any
On 02 Jul 2015, at 22:50, Alexander Shorin kxe...@gmail.com wrote:
On Thu, Jul 2, 2015 at 11:31 PM, Jan Lehnardt j...@apache.org wrote:
I really like your attempt to preserve this 1.x-ism for small clusters.
I’m not sure I feel really good about this though, for the same reasons
that
On 02 Jul 2015, at 10:12, Alexander Shorin kxe...@gmail.com wrote:
Hi Robert,
On Wed, Jul 1, 2015 at 4:14 PM, Robert Kowalski r...@kowalski.gd wrote:
Here are the things I found out or I had to explain:
- the feature is not intended for more than 5, maybe 10 nodes as it is
not
Hi folks,
in the last week we got a new API endpoint:
```
_node/fqdn/_config
```
Using this endpoint you can reach every node in a cluster by
specifying the name of the node.
This sound cool to me for using it in Fauxton as the Fauxton team
wants to keep the ability to configure CouchDB using
