[
https://issues.apache.org/jira/browse/LUCENE-9020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16977262#comment-16977262
]
Uwe Schindler commented on LUCENE-9020:
---------------------------------------
So INFRA responden and told us that the Maven approach is the way to go.
Basically it means we use a subdirectory of our website (like
"lucene.apache.org/docs") and tell them to link them to a folder in subversion.
We'd do a SVN COPY of the old content there (so we can delete the old CMS
website with extpaths). There is only the problem of the "old" location of
documentation and refguide, which is splattered through the website logic:
Maven uses symlinks, but that's impossible to setup with GIT. And adding tons
of Alias directives is also bad. So my proposal is to add perm redirects using
a regex on {{lucene.apache.org/java/\\d_\\d_\\d}} and similar.
The webserver config (or htaccess) would then contain a config that makes the
svn folder visible on the website (only in that subdirectory)below a single
location. Users are redirected by above
An alternative would be to use AliasMatch:
https://httpd.apache.org/docs/2.4/mod/mod_alias.html#aliasmatch
> Find a way to publish Solr RefGuide without checking into git
> -------------------------------------------------------------
>
> Key: LUCENE-9020
> URL: https://issues.apache.org/jira/browse/LUCENE-9020
> Project: Lucene - Core
> Issue Type: Sub-task
> Reporter: Jan Høydahl
> Priority: Major
>
> Currently we check in all versions of RefGuide (hundreds of small html files)
> into svn to publish as part of the site. With new site we should find a
> smoother way to do this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
