[
https://issues.apache.org/jira/browse/LUCENE-9020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16957251#comment-16957251
]
Jan Høydahl commented on LUCENE-9020:
-------------------------------------
{quote}The process to publish today is as simple as {{svn import <files>
<production repo>}}, which is rather smooth from that point of view, so I feel
like you may be trying to articulate a different problem?
{quote}
Yes, that is true. If we're going to abandon the SVN based CMS for our website
(it is deprecated) and migrate to GIT for hosting the site, we would probably
face issues if we continue to dump and check in gigabytes of small HTML files
into the git repo, as it won't handle it as well as SVN. That's also the reason
we have a hack today to import those static files directly into the production
tree instead of checking them into staging, which would kill the CMS.
So instead of limiting ourselves to doing things the same way as before which
was due to how the old CMS worked, we should instead ask ourselves "How would
we do it today?".
Tons of open source projects host their docs on ReadTheDocs and similar and
they offer nice services with versioning, search, building docs from git branch
etc.
We should probably collaborate with INFRA to see if they have some advice. We
could of course just start with the equivalent of what we do now and check in
the ref guide HTML into the new lucene-site git repo and improve on that if it
does not scale or whatever.
> 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
