> On 17 May 2017, at 04:03, Jeff King <peff@xxxxxxxx> wrote: > > On Tue, May 16, 2017 at 09:56:37PM -0400, Samuel Lijin wrote: > >> So I've finally found the time to get everything set up (in the >> process discovering that remote_genbook2 consistently induces a >> segfault in VirtualBox's networking driver, impressively enough) and >> am taking a look at how much work it would take to get the site >> running on AWS EC2/DO or some other hosting provider. >> >> Some things I'm wondering about: >> >> - You mentioned a lot of people reaching out off-list about hosting >> options. Do any of them look particularly appealing at the moment? > > Yes. I actually have stuff to announce there soon, but was holding off > until the final pieces are in place. But basically, the architecture > would remain largely the same, but hosted on community-owned accounts > (that I can share access to), with sponsorship from various hosting > services. > >> - How do I set up the ES service? > > 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? - Lars