Github user janl commented on the pull request:
https://github.com/apache/couchdb-fauxton/pull/474#issuecomment-115829193
I totally understand that âmake it prettyâ is not a good approach, and
I donât think that is whatâs being asked here.
It was quite hard to get the technical underpinnings right and to show them
off @robertkowalski made the little demo of what it could look like. I don't
think a design-first approach would have worked here, but I might be wrong.
From a design perspective, feel free to start from scratch! :)
As for the questions:
> How many nodes do we need to consider here? for example, could you start
with one node and scale up to a thousand?
In theory, this could mean 100s and 1000s of nodes, but in practice, there
are limits. The scenario for this is to get people to set up small-ish
clusters, say 3-10, maybe 20 nodes and let them do this manually and guide them
along.
If users get into the 20+ range of nodes, they will (very likely) use
automated ways to set up their cluster nodes, and they could/would use the same
system to roll out config changes across a cluster.
I donât expect anyone updating a config value on 1000 nodes through this.
Now this poses an interesting question: CouchDB traditionally has not added
any features that would break at scale. Itâs not that Fauxton couldnât
handle 1000 nodes here, but it wouldnât be practical for an end-user to use
this, so should we have this feature or not?
I come down at the âit will be obvious when this doesnât
scaleâ-point, so I welcome the feature. And yes, it shouldnât break when a
users has 1000 nodes, but it is totally fine if it is impractical. We might
even show a notice that says as much, when you go over, say 10 or 20 or 50
nodes.
> If you had a thousand, would you have to page through it?
Iâd say this is up to the designer, I wouldnât feel comfortable
proposing a solution, just the technical constraints.
> Also, could we put CORS to configure page instead of making it separate?
Iâm not sure what this refers to.
---
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.
---
