[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lilypond-bug
Subject:    Re: Issue 3191 - Fix relative links
From:       "Phil Holmes" <mail () philholmes ! net>
Date:       2013-02-24 11:28:24
Message-ID: kgctgo$ufu$1 () ger ! gmane ! org
[Download RAW message or body]

"Felix Janda" <felix.janda@posteo.de> wrote in message 
news:20130224111628.GA7647@gauss...
> On 02/22/13 at 08:48pm, Felix Janda wrote:
>> To solve this issue I think the following steps suffice:
>>
>> 1. Replace links like http://lilypond.org/website/manuals.html by
>> http://lilypond.org/manuals.html. See the patch below. Then nobody should
>> need to know that http://lilypond/website exists (including search
>> engines).
>>
>> 2. Modify the root .htaccess to 301 redirect all traffic from
>> http://lilypond.org/website to the corresponding url without /website.
>>
>> 3. Make the depth variable in scripts/build/create-weblinks-itexi.py
>> dependent on whether the Docs are being built for local enjoyment or for
>> the server. That's probably not trivial with the current build system.
>
> Attached are patches against the current git master, one for each step.
>
> I've tested the Apache configuration locally.
>
> I'd be happy if someone could test that it now works correctly for both
> the local documentation and lilypond.org since I haven't been able to
> successfully "make web", yet.
>
> Felix
>
> BTW some things in the .htaccess file are unecessary or misleading since
> %{ENV:WEB} is unconditionally set to /website.
>

The only people likely to be able to check these are Graham and myself.  I'm 
loathe to delve too deeply, since I don't understand the Apache stuff, nor 
why the website stuff was put there in the first place.  Graham?

-- 
Phil Holmes
Bug Squad 




[prev in list] [next in list] [prev in thread] [next in thread]