unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "Collin J. Doering" <collin@rekahsoft.ca>
Cc: guix-devel@gnu.org
Subject: Re: New North American based Guix Substitute Server, cuirass.genenetwork.org Now Available
Date: Thu, 11 Jul 2024 12:01:13 +0200	[thread overview]
Message-ID: <87a5io2qom.fsf@gnu.org> (raw)
In-Reply-To: <871q46ytyn.fsf@rekahsoft.ca> (Collin J. Doering's message of "Sat, 06 Jul 2024 19:35:44 -0400")

Hi Collin,

"Collin J. Doering" <collin@rekahsoft.ca> skribis:

> I am excited to announce that Guix substitutes (for x86_64) are now available in North America, thanks to the generous contribution of server hardware and infrastructure from GeneNetwork.org.
>
> This new server enhances the availability and redundancy of Guix substitutes, ensuring a more robust and reliable experience for users in North America.
>
> We will be posting a detailed blog article about the setup of the build farm in the coming weeks, but the Guix system configuration and notes about its setup can be found at https://git.rekahsoft.ca/rekahsoft/guix-north-america/. Stay tuned for more information!

Congrats!  I’m confident many in the Americas will find it useful.

If I’m not mistaken, the machine is configured¹ to take substitutes from
ci.guix and bordeaux.guix.  It would be interesting (but obviously more
expensive CPU-wise…) to not do that as a way to get diverse builds that
can be checked with ‘guix challenge’.

Thanks,
Ludo’.

¹ https://git.rekahsoft.ca/rekahsoft/guix-north-america/src/branch/master/.guix/guix-na/config/balg02.scm


  reply	other threads:[~2024-07-11 10:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-06 23:35 New North American based Guix Substitute Server, cuirass.genenetwork.org Now Available Collin J. Doering
2024-07-11 10:01 ` Ludovic Courtès [this message]
2024-07-23 14:42   ` Collin J. Doering

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=87a5io2qom.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=collin@rekahsoft.ca \
    --cc=guix-devel@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).