Hi,
Ludovic Courtès writes:
> Peng Mei Yu skribis:
>
>> Ludovic Courtès writes:
>>
>>> Ricardo Wurmus skribis:
>>>
We need to make sure that *all* the files produced by “guix publish”
have correct permissions; IIRC some of the files are not readable at all
by users other than the
Hi!
Peng Mei Yu skribis:
> Ludovic Courtès writes:
>
>> Ricardo Wurmus skribis:
>>
>>> We need to make sure that *all* the files produced by “guix publish”
>>> have correct permissions; IIRC some of the files are not readable at all
>>> by users other than the owner of the files.
>>
>> Oops, I
Hello,
Ludovic Courtès writes:
> Ricardo Wurmus skribis:
>
>> We need to make sure that *all* the files produced by “guix publish”
>> have correct permissions; IIRC some of the files are not readable at all
>> by users other than the owner of the files.
>
> Oops, I had forgotten, my bad. I’ll p
Dear,
Thank you.
In case you need arguments to convince academics, this satellite Guix
project could help:
https://hpc.guix.info/about/
On Thu, 05 Nov 2020 at 09:55, Peng Mei Yu wrote:
> Jonathan Brielmaier writes:
>>
>> I think we should discuss if Guix can support your effort money wise
Hi,
Peng Mei Yu skribis:
> Ludovic Courtès writes:
>
>>> Then a mirror site can simply pull the directory
>>> /var/cache/guix/publish/nar from the Berlin server and serve this
>>> directory through a static HTTP server. There will be cache misses.
>>> But guix-daemon will safely fallback to the
Hello,
Ludovic Courtès writes:
>> Then a mirror site can simply pull the directory
>> /var/cache/guix/publish/nar from the Berlin server and serve this
>> directory through a static HTTP server. There will be cache misses.
>> But guix-daemon will safely fallback to the next server in
>> substitu
Hi,
Ricardo Wurmus skribis:
> Ludovic Courtès writes:
>
>> The simplest solution for now (I think that’s what Ricardo & co. had in
>> mind) would be for you to retrieve /var/cache/guix/publish on your
>> server, as is, and then run ‘guix publish’ on your sever: it will know
>> where to find fil
Ludovic Courtès writes:
> The simplest solution for now (I think that’s what Ricardo & co. had in
> mind) would be for you to retrieve /var/cache/guix/publish on your
> server, as is, and then run ‘guix publish’ on your sever: it will know
> where to find files. As I wrote to Jonathan, you can
Hello!
Peng Mei Yu skribis:
> This proposal aims to solve an old problem. Make it easier to setup a
> mirror server for the official substitute server and prevent future
> complaints from China residents about network speed.
Just so you know: we’re aware of this problem and agree that it needs
Hi,
Jonathan Brielmaier skribis:
> I'm running myself a smaller cuirass+publish server and I have
> configured the caching on the nginx side and not with `guix publish`.
This is suboptimal because then your /nar responses lack the
‘Content-Length’ header (‘guix publish’ cannot provide that head
Hi Jonathan,
Jonathan Brielmaier writes:
> I'm running myself a smaller cuirass+publish server and I have
> configured the caching on the nginx side and not with `guix publish`.
>
> So my cache resides in:
> /var/cache/nginx/nar/
>
> For me it has a dramatic speed up on my German server reaching
Hi Peng Mei Yu,
first of all a big thank you for making the Guix experience in China
much nicer!
I'm running myself a smaller cuirass+publish server and I have
configured the caching on the nginx side and not with `guix publish`.
So my cache resides in:
/var/cache/nginx/nar/
For me it has a dra
12 matches
Mail list logo
