From: zimoun <zimon.toutoune@gmail.com>
To: Jack Hill <jackhill@jackhill.us>
Cc: guix-devel@gnu.org
Subject: Re: extend ’guix archive’?
Date: Tue, 21 Dec 2021 11:49:17 +0100 [thread overview]
Message-ID: <86pmpqqlle.fsf@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2112210033050.9433@marsh.hcoop.net>
Hi,
On Tue, 21 Dec 2021 at 00:50, Jack Hill <jackhill@jackhill.us> wrote:
> I think it would be great if one of the pastures to which we herd the nars
> would be a free and open source software mirror site. In my experience,
> these are usually some static web hosting in front of a large disk with a
> place to run scripts to sync the content. A database server may not be
> available. I'd like to support this use case because I think it is a great
> way to build bridges to the communities who run or gather around these
> mirrors.
Well, from my understanding, it looks like P2P distribution. ;-)
> I'd also like the ability fetch nars directly from the local-to-me mirror
> rather than having them be proxied through a far way server.
Well, from my understanding, it looks like CDN. :-)
> One of the things that I really like and find empowering about Guix is
> that the developer/system administration tools are as available, easy to
> use, and convenient as the every day tooling. To the extent possible, I
> think that we should strive to make our syncing/mirroring solution
> practical to run for local, small setups, and not require project-scale
> infrastructure or coordination between many programs that are not captured
> in a Guix service.
At some point I agree, but I would like to mitigate. The issue is
scaling up. It is not easy and it requires a lot of effort, solve a
large range of bugs or design issues, etc. Scaling up comes with a
cost. To be concrete, one example: Cuirass migrated from SQLite to
PostgreSQL. And at some point, the project should rely on existing
bullet-proof solutions for scaling up instead of reinventing the wheel
with all what it implies and focus on the project strengths. And
bullet-proof solutions able to scale often mean not-so-easy small
setups. Well, hard to find the right balance. :-)
Cheers,
simon
next prev parent reply other threads:[~2021-12-21 10:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 16:48 Mid-December update on bordeaux.guix.gnu.org Christopher Baines
2021-12-15 22:49 ` zimoun
2021-12-16 0:20 ` Christopher Baines
2021-12-16 11:05 ` zimoun
2021-12-16 12:48 ` Christopher Baines
2021-12-16 14:25 ` Andreas Enge
2021-12-21 9:53 ` Redundancy for source code and Disarchive Ludovic Courtès
2021-12-17 9:00 ` Mid-December update on bordeaux.guix.gnu.org Andreas Enge
2021-12-17 9:03 ` Andreas Enge
2021-12-20 22:07 ` Ludovic Courtès
2021-12-20 22:52 ` extend ’guix archive’? zimoun
2021-12-21 5:50 ` Jack Hill
2021-12-21 10:49 ` zimoun [this message]
2022-02-04 12:48 ` Christopher Baines
2021-12-21 9:39 ` Ludovic Courtès
2021-12-21 10:32 ` zimoun
2022-02-04 12:36 ` Christopher Baines
2022-01-06 13:26 ` Mid-December update on bordeaux.guix.gnu.org Christopher Baines
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=86pmpqqlle.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=jackhill@jackhill.us \
/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).