Arvados

Ready for review at 6160b7425d9da6cc9d245b7cc754e81427f8ac9c on branch 17591-doc-improvement

I think the new "if you have this then do that" table is a huge improvement.

I noticed a (pre-existing) missing "the" in doc/install/install-manual-prerequisites.html.textile.liquid: "You can run several services on same node, but ..."

Re note in description "talks about hostnames but these are usually virtual hosts"... would it be more clear to say "DNS name" instead of "hostname" when referring to a name in a URL as opposed to the thing reported by the hostname command? E.g., in "each distinct hostname requires a valid, matching TLS certificate" we could say "each distinct DNS name"?

I suspect in many cases wildcard TLS and DNS are possible, but require extra effort, and people will be inclined to avoid the extra effort by going with the "other" column, even though the text assures them it will be "easier" with wildcards. Should we mention here that skipping the wildcards will have consequences later ("this will disable some features that allow users to view Arvados-hosted data in their browsers" or something like that?), rather than let people think they're taking the easy route only to find out later that they need to come back and reconfigure.

Tom Clegg wrote:

I think the new "if you have this then do that" table is a huge improvement.

I noticed a (pre-existing) missing "the" in doc/install/install-manual-prerequisites.html.textile.liquid: "You can run several services on same node, but ..."

Fixed!

Re note in description "talks about hostnames but these are usually virtual hosts"... would it be more clear to say "DNS name" instead of "hostname" when referring to a name in a URL as opposed to the thing reported by the hostname command? E.g., in "each distinct hostname requires a valid, matching TLS certificate" we could say "each distinct DNS name"?

OK, changed.

I suspect in many cases wildcard TLS and DNS are possible, but require extra effort, and people will be inclined to avoid the extra effort by going with the "other" column, even though the text assures them it will be "easier" with wildcards. Should we mention here that skipping the wildcards will have consequences later ("this will disable some features that allow users to view Arvados-hosted data in their browsers" or something like that?), rather than let people think they're taking the easy route only to find out later that they need to come back and reconfigure.

Yeah, good idea, I've added some language like that.

I've also made an explicit mention of the 'TrustAllContent' flag on the keep-web urls page, and fixed the explanation for that flag in the default config file, it was missing a word.

Ready for another look at 1c5a21a73b2e5281cea17db4ae5f4d367dee1ee4

LGTM, thanks!