Ricardo Wurmus writes:
> Ludovic Courtès writes:
>
>> Roel Janssen skribis:
>>
>>> We need to add the following line to the response header at
>>> hydra.gnu.org:
>>>
>>> Access-Control-Allow-Origin: "http://www.gnu.org";
>>>
>>> Here's how to do it:
>>> http://enable-cors.org/server_nginx.h
Ludovic Courtès writes:
> Roel Janssen skribis:
>
>> We need to add the following line to the response header at
>> hydra.gnu.org:
>>
>> Access-Control-Allow-Origin: "http://www.gnu.org";
>>
>> Here's how to do it:
>> http://enable-cors.org/server_nginx.html
>>
>> Which boils down to adding
Roel Janssen skribis:
> We need to add the following line to the response header at
> hydra.gnu.org:
>
> Access-Control-Allow-Origin: "http://www.gnu.org";
>
> Here's how to do it:
> http://enable-cors.org/server_nginx.html
>
> Which boils down to adding this line to the nginx config:
> add
Ludovic Courtès writes:
> Roel Janssen skribis:
>
>> Ludovic Courtès writes:
>>
>>> Roel Janssen skribis:
>>>
Ludovic Courtès writes:
> Roel Janssen skribis:
>>>
>>> [...]
>>>
>> We might need to add a HTTP header from the GNU server to allow
>> loading data from external
Roel Janssen skribis:
> Ludovic Courtès writes:
>
>> Roel Janssen skribis:
[...]
>>> Yes, I think it only works when the origin is hydra.gnu.org. I
>>> contacted the sysadmins again to figure this out. Could you leave the
>>> page there for a couple of days? That way I can give them a live
Ludovic Courtès writes:
> Roel Janssen skribis:
>
>> Ludovic Courtès writes:
>
> [...]
>
>>> Good! I applied the patch and deployed the new web page:
>>>
>>> https://www.gnu.org/software/guix/packages/
>>>
>>> However, it’s still failing:
>>>
>>> 17:00:49.802 Cross-Origin Request Blocked: T
Roel Janssen skribis:
> Ludovic Courtès writes:
[...]
>> Good! I applied the patch and deployed the new web page:
>>
>> https://www.gnu.org/software/guix/packages/
>>
>> However, it’s still failing:
>>
>> 17:00:49.802 Cross-Origin Request Blocked: The Same Origin Policy
>> disallows readi
Roel Janssen skribis:
> Ludovic Courtès writes:
>
>> Roel Janssen skribis:
>>
>>> Ludovic Courtès writes:
>>>
Roel Janssen skribis:
>>
>> [...]
>>
> We might need to add a HTTP header from the GNU server to allow
> loading data from external sources:
>
> https://en.wikipe
Ludovic Courtès writes:
> Roel Janssen skribis:
>
>> Ludovic Courtès writes:
>>
>>> Roel Janssen skribis:
>
> [...]
>
We might need to add a HTTP header from the GNU server to allow
loading data from external sources:
https://en.wikipedia.org/wiki/Cross-origin_resource_sha
Roel Janssen skribis:
> Ludovic Courtès writes:
>
>> Roel Janssen skribis:
[...]
>>> We might need to add a HTTP header from the GNU server to allow
>>> loading data from external sources:
>>>
>>> https://en.wikipedia.org/wiki/Cross-origin_resource_sharing
>>
>> Indeed, because here the requ
>From 738c4035b3f8978622e96c83c9bd7b9679ce747c Mon Sep 17 00:00:00 2001
From: Roel Janssen
Date: Mon, 4 Jan 2016 21:05:02 +0100
Subject: [PATCH] website: packages: Add build status icons in the expanded
view.
* website/www/packages.scm (package->sxml): Wrap the build status link in a div
and p
Ludovic Courtès writes:
> Roel Janssen skribis:
>
>> I've attached a patch that adds status icons to the links in the
>> expanded view. It only loads when the user clicks on "expand".
>
> This is great!
>
> Minor things: I would move the patch list above the status, and remove
> the “status:” he
Roel Janssen skribis:
> I've attached a patch that adds status icons to the links in the
> expanded view. It only loads when the user clicks on "expand".
This is great!
Minor things: I would move the patch list above the status, and remove
the “status:” heading.
> We might need to add a HTTP h
>From a37d4ff3d0a0abe676ce7458d11f8797d6bd30ac Mon Sep 17 00:00:00 2001
From: Roel Janssen
Date: Tue, 24 Nov 2015 14:08:34 +0100
Subject: [PATCH] website: packages: Add build status icons in the expanded
view.
* website/www/packages.scm (package->sxml): Wrap the build status link in a div
and
Roel Janssen skribis:
> Ludovic Courtès writes:
>
>> Roel Janssen skribis:
>>
>>> Ludovic Courtès writes:
>>>
Roel Janssen skribis:
> The list of packages included in Guix [1] provides links to the build
> status of each package in the details. I would like to provide this
>>
On Sat, Nov 21, 2015 at 04:24:50PM +0100, Roel Janssen wrote:
> > IMO it wouldn’t be very useful since the list is updated once a day.
>
> Ok. If we can instead fetch the status of all packages on all
> architectures in one HTTP request (using javascript on the client-side),
> would that be accept
Ludovic Courtès writes:
> Roel Janssen skribis:
>
>> Ludovic Courtès writes:
>>
>>> Roel Janssen skribis:
>>>
The list of packages included in Guix [1] provides links to the build
status of each package in the details. I would like to provide this
information in a column after "
Mark H Weaver writes:
> Roel Janssen writes:
>
>> Eric Bavier writes:
>>
>>> On 2015-11-19 13:57, Mark H Weaver wrote:
Roel Janssen writes:
> The list of packages included in Guix [1] provides links to the build
> status of each package in the details. I would like to provid
Roel Janssen skribis:
> Ludovic Courtès writes:
>
>> Roel Janssen skribis:
>>
>>> The list of packages included in Guix [1] provides links to the build
>>> status of each package in the details. I would like to provide this
>>> information in a column after "Package details", either as an icon
> Maybe we could instead determine the build status at the time we
> generate the website's package list?
Or trigger the page generation on a build. I don't think that will be
a problem for Hydra compared to other activity ;)
Pj.
--
Ludovic Courtès writes:
> Roel Janssen skribis:
>
>> The list of packages included in Guix [1] provides links to the build
>> status of each package in the details. I would like to provide this
>> information in a column after "Package details", either as an icon or as
>> a count (e.g. 3/4 build
Roel Janssen writes:
> Eric Bavier writes:
>
>> On 2015-11-19 13:57, Mark H Weaver wrote:
>>> Roel Janssen writes:
>>>
The list of packages included in Guix [1] provides links to the build
status of each package in the details. I would like to provide this
information in a colum
Roel Janssen skribis:
> The list of packages included in Guix [1] provides links to the build
> status of each package in the details. I would like to provide this
> information in a column after "Package details", either as an icon or as
> a count (e.g. 3/4 builds succeeded). This provides a n
Eric Bavier writes:
> On 2015-11-19 13:57, Mark H Weaver wrote:
>> Roel Janssen writes:
>>
>>> The list of packages included in Guix [1] provides links to the build
>>> status of each package in the details. I would like to provide this
>>> information in a column after "Package details", eith
On 2015-11-19 13:57, Mark H Weaver wrote:
Roel Janssen writes:
The list of packages included in Guix [1] provides links to the build
status of each package in the details. I would like to provide this
information in a column after "Package details", either as an icon or
as
a count (e.g. 3/4
Roel Janssen writes:
> The list of packages included in Guix [1] provides links to the build
> status of each package in the details. I would like to provide this
> information in a column after "Package details", either as an icon or as
> a count (e.g. 3/4 builds succeeded). This provides a ni
Dear list,
The list of packages included in Guix [1] provides links to the build
status of each package in the details. I would like to provide this
information in a column after "Package details", either as an icon or as
a count (e.g. 3/4 builds succeeded). This provides a nicer overview for
th
27 matches
Mail list logo
