Re: Broken Pages After Commits (Master)
| From: | Hannes Magnusson | Date: | Sun, 15 Dec 2013 02:41:45 +0000 |
| Subject: | Re: Broken Pages After Commits (Master) | ||
| References: | 1 2 3 4 | Groups: | php.webmaster |
| Request: | Send a blank email to php-webmaster+get-17631@lists.php.net to get a copy of this message | ||
On Sat, Dec 14, 2013 at 10:07 AM, Hannes Magnusson <bjori@php.net> wrote:
> On Sat, Dec 14, 2013 at 9:54 AM, Daniel Brown <danbrown@php.net> wrote:
>> On Sat, Dec 14, 2013 at 12:49 PM, Hannes Magnusson <bjori@php.net> wrote:
>>>
>>> To be honest, I like it better unstyled then how it was :)
>>> There is also so much weird inline styling that has to be killed
>>> before we can make it better again.
>>
>> You might, but I don't. And I'm the one who uses it most. ;-P
>>
>>> Where did status.php.net come from and how does that work? How is it
>>> different from master ?
>>
>> I built it last year or the year before. Mirror maintainers use
>> it to see how their mirrors look from our end.
>
>
> How does it work?
>
> Is it a partial checkout from master?
> I'm asking cause I don't see a reason why that doesn't work, but
> viewing the same thing on master works just fine.
It was using the same sources, but pointed to the network subdirectory
so the new /shared/ folder wasn't being served. Loading the
stylesheets returned 200 OK, but was actually hitting api.php which
had die() in it without changing the status code.
I added an apache Alias and new Directory config for the /shared/ path
and it seems to work.
I would however rather like to move this into its own repo, it is
weird that it is serving a subdirectory from master - which is also
accessible from master?
You ok with me migrating it over to web-status repo?
Or maybe call it web-network-status ?
-Hannes