Re: git-scm.com status report

From: Jeff King <peff@peff.net>
Date: May 18, 2017, 15:42 UTC
Message-ID: <20170518154159.s2ysocfzlf2ffgqg@sigill.intra.peff.net>
In-Reply-To: <469A925D-E5E4-4B9D-8AE2-A23DBA3595AE@gmail.com>

On Thu, May 18, 2017 at 02:06:16PM +0200, Lars Schneider wrote:

Show 16 quoted lines

> > I haven't ever tried to do this in the local development environment.
> > The production site currently just use a cloud-hosted ES (Bonsai). They
> > have free "Sandbox" plans for testing, so you could probably use that as
> > a test resource after setting up the relevant environment variables. Or
> > alternatively, I think ElasticSearch folks produce binary builds you can
> > try, and you could host locally.
> > 
> > There's a rake job that inserts documents into the search index (see
> > lib/tasks/search.rake).
> 
> Disclaimer: I am jumping in here without much knowledge. Feel free
> to ignore me :-)
> 
> In our TravisCI builds we create the AsciiDoc/Doctor documentation
> already. Couldn't we push that result to some static hosting service?
> Would that help in any way with git-scm.com?

Not really. The site builds the asciidoctor documentation already via an automated job. This question was just about putting it into the search index (which also happens in production with an automated job; this is just about setting up the search database). So I don't think there's any real problem to be solved with respect to generating pages.

-Peff