Hi,

Peng Mei Yu <pengme...@riseup.net> 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 next server in
>>> substitute-urls.
>>
>> 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/should also run
>> nginx on top of that as a proxy to your local ‘guix publish’.
>
> I am afraid having to install Guix and run 'guix publish' will be a
> major obstacle for most mirror sites, especially when their maintainers
> have no previous experience with Guix and have no interest in learning a
> new software and do not want to pollute their server with an unknown
> software and do not want to increase maintenance burden. This is the
> simplest solution on our side, but a complex solution on mirror site
> maintainers' side.

Hmm yes.  I was assuming that someone running a Guix mirror wouldn’t
have troubles running Guix, but there may be cases where this is not the
case.

> I guess a complex Nginx URL rewrite rule might also convert the URL into
> real filename in the cache.  Can anyone familiar with Nginx explain?

I’m not super familiar, but I think it’s doable.

Ludo’.

Reply via email to