[
https://issues.apache.org/jira/browse/SOLR-10299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16495503#comment-16495503
]
Greg Stein commented on SOLR-10299:
-----------------------------------
>From HipChat: "But we wouldn't want it exposed to the open Internet, so
>accessing such a service from the documentation pages securely would require
>server side code."
HTTPd config could easily limit the pages to (say) Apache committers, without
any server side code.
Also note that if you're limiting the audience, then HA/failover should not be
needed. It doesn't sound like you would need that for the smaller audience. Our
VMs have great uptime, so failures would tend to be the software stack which
generally means HA won't save you.
Point being: you can simplify your deployment.
(and also, that we tend to provide just *one* VM to each project, so asking for
"several" is typically a non-starter)
Greg Stein
Infrastructure Administrator, ASF
> Provide search for online Ref Guide
> -----------------------------------
>
> Key: SOLR-10299
> URL: https://issues.apache.org/jira/browse/SOLR-10299
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: documentation
> Reporter: Cassandra Targett
> Priority: Major
>
> The POC to move the Ref Guide off Confluence did not address providing
> full-text search of the page content. Not because it's hard or impossible,
> but because there were plenty of other issues to work on.
> The current HTML page design provides a title index, but to replicate the
> current Confluence experience, the online version(s) need to provide a
> full-text search experience.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
