unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Peng Mei Yu <pengmeiyu@riseup.net>
Cc: guix-devel@gnu.org
Subject: Re: Make guix-publish's URL identical to cache file name
Date: Thu, 12 Nov 2020 21:37:13 +0100	[thread overview]
Message-ID: <87lff6gvly.fsf@gnu.org> (raw)
In-Reply-To: <87o8k7utf2.fsf@riseup.net> (Peng Mei Yu's message of "Mon, 09 Nov 2020 10:59:29 +0800")

Hi,

Peng Mei Yu <pengmeiyu@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	other threads:[~2020-11-12 20:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-04  8:46 Make guix-publish's URL identical to cache file name Peng Mei Yu
2020-11-04 12:01 ` Jonathan Brielmaier
2020-11-05  1:55   ` Peng Mei Yu
2020-11-13 12:53     ` zimoun
2020-11-06  9:51   ` Ludovic Courtès
2020-11-06  9:55 ` Ludovic Courtès
2020-11-07  6:03   ` Ricardo Wurmus
2020-11-08 17:08     ` Ludovic Courtès
2020-12-09  8:29       ` Peng Mei Yu
2020-12-14  9:54         ` Ludovic Courtès
2021-01-11  2:13           ` Peng Mei Yu
2020-11-09  2:59   ` Peng Mei Yu
2020-11-12 20:37     ` Ludovic Courtès [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lff6gvly.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=pengmeiyu@riseup.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).