unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Nala Ginrut <mulei@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Support rsync to help Chinese users to setup mirrors
Date: Thu, 08 Aug 2019 23:35:53 +0200	[thread overview]
Message-ID: <87imr7wdae.fsf@elephly.net> (raw)
In-Reply-To: <87k1bn8p0f.fsf@debian>


Hi,

> There is the national firewall in China, so common users have difficult
> to download Guix packages in a fair speed. This may hardly understand by
> people outside China, but that is the fact.

I’m aware.  I lived with the firewall for ~7 years and would like to
make sure that people who are subjected to the firewall can use Guix
without being restricted.

> We hope there's a way like rsync to sync /gnu/store with upstream, so
> that we can provide a faster cache for Chinese users.

I think it may be best to just sync the cache of nars and narinfos.

Would rsync over SSH be sufficient or does it have to be rsyncd on the
default rsync port?  (SSH will be easier for me because then I don’t
need to apply for another port to be opened at the institute firewall.)

I’ve also been looking into our options for restricting rsync access via
chroot or namespaces.  Looks like the easiest way to do this is to have
an rsync user account that is restricted to a chroot with access to the
nar cache.

--
Ricardo

  reply	other threads:[~2019-08-08 21:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-01 10:56 Support rsync to help Chinese users to setup mirrors Nala Ginrut
2019-08-01 14:22 ` Ricardo Wurmus
2019-08-02  7:35   ` Nala Ginrut
2019-08-07  6:31     ` Nala Ginrut
2019-08-07  7:44       ` Ricardo Wurmus
2019-08-08  9:35         ` Nala Ginrut
2019-08-08 11:39           ` Ricardo Wurmus
2019-08-08 18:56             ` Nala Ginrut
2019-08-08 21:35               ` Ricardo Wurmus [this message]
2019-08-09  5:52                 ` Nala Ginrut
2019-08-09  8:52                   ` Ricardo Wurmus
2019-08-10  8:18                     ` Nala Ginrut

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=87imr7wdae.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=mulei@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).