Re: [Boost-build] Root index file.

Subject: Re: [Boost-build] Root index file.
From: Vladimir Prus (ghost_at_[hidden])
Date: 2014-10-31 12:52:05

On 07/14/2014 10:34 AM, Daniel James wrote:
> On 14 July 2014 06:33, Vladimir Prus <ghost_at_[hidden]> wrote:
>> On 07/13/2014 10:08 PM, Daniel James wrote:
>>>
>>> Hi,
>>>
>>> Every module should have an index.html at its root, so that it can be
>>> easily linked to. Would it be possible to create one for the build
>>> module? I think not having one will also cause problems if we update
>>> the documentation at http://www.boost.org/boost-build2/
>>
>>
>> I certainly can move index.html out of website subdir to the top level.
>>
>> The question though, is how do you expect http://www.boost.org/boost-build2/
>> to be put together in future? I think the previous approach with unpacking
>> of
>> nightly build is too contrived, so maybe the above URL can just
>> transparently
>> proxy to github page (i.e. something like http://boostorg.github.io/build),
>> and the gh-pages branch would be updated by a nightly build process?
>
> Whatever you prefer. I upload the documentation using rsync, which is
> pretty simple if you've got an account and your ssh keys setup.
> Although this is also for the offline documentation, not just for the
> website.

Daniel,

would it be possible to setup transparent proxy from

        http://boost.org/boost-build2

to

        http://boostorg.github.io/build/

And also do the same for http://boost.org/b2 and http://boost.org/build, if possible?

By transparent I mean the setup described here:

        http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxyrequests

where apache will connect to boostorg.github.io itself, and pass the request over,
as opposed to redirecting the client. I think it's slightly preferable as the
user won't have to remember different domain names.

If that's done, all existing hackery to serve boost.build docs can be disabled.
The destination is already up.

Thanks,
Volodya