Hi, [...]
>> >> OK! I guess we could try the simplest path first and complicate it if >> there are issues with it. There already is a rsync service exposing >> /var/cache/guix/publish on berlin: >> >> --8<---------------cut here---------------start------------->8--- >> (rsync-module >> (name "substitutes") >> (file-name "/var/cache/guix/publish")) >> --8<---------------cut here---------------end--------------->8--- > > Good to know! I think it's already exposed? > > $ rsync --list-only rsync://berlin.guix.gnu.org/ > web-pdf > web-video > web-audio > web-cuirass > web-cuirass-manual > disarchive > substitutes > web-guix-hpc-videos Interesting. It looks like it is; from berlin (ss -ltpn | grep 873) --8<---------------cut here---------------start------------->8--- 0.0.0.0:873 --8<---------------cut here---------------end--------------->8--- So it listens to all IPv4 interfaces on the rsync port. From home: --8<---------------cut here---------------start------------->8--- $ rsync --list-only rsync://berlin.guix.gnu.org/ web-pdf web-video web-audio web-cuirass web-cuirass-manual disarchive substitutes web-guix-hpc-videos $ telnet berlin.guix.gnu.org 873 Trying 141.80.181.40... Connected to berlin.guix.gnu.org. Escape character is '^]'. @RSYNCD: 32.0 sha512 sha256 sha1 md5 md4 --8<---------------cut here---------------end--------------->8--- Looks like it's already exposed indeed. I wasn't aware of that, but it makes sense I guess, since we've been mirroring the website for a while to bayfront, IIUC. So feel free to experiment already! I guess even if you only do a partial sync of the whole collection for guix-publish to work correctly from it, you'll want to ensure that you don't lack any .narinfo file corresponding to a nar. Since these files are small on disk, the easiest approach would be to rsync all of them first, then sync the .nar after, I suppose. -- Thanks, Maxim
