From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Make guix-publish's URL identical to cache file name
Date: Sat, 07 Nov 2020 07:03:59 +0100 [thread overview]
Message-ID: <87d00pya7k.fsf@elephly.net> (raw)
In-Reply-To: <87mtzu24ii.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> 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/should also run
> nginx on top of that as a proxy to your local ‘guix publish’.
>
> Ricardo, can you remind us what the next steps would be?
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.
Once that’s done we just need to start the rsync daemon again,
preferably as a shepherd service.
--
Ricardo
next prev parent reply other threads:[~2020-11-07 6:02 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 [this message]
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
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=87d00pya7k.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
/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).