all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org, guix-europe@gnu.org
Subject: Re: Using the Hetzner Cloud
Date: Mon, 17 Feb 2020 21:39:09 +0100	[thread overview]
Message-ID: <87y2t1kkya.fsf@elephly.net> (raw)
In-Reply-To: <87o8txynuv.fsf@cbaines.net>


Christopher Baines <mail@cbaines.net> writes:

> Coupled with this, I think there are some services (hpc.guix.info, ...)
> it would be nice to move off bayfront (a machine in Bordeaux) to
> somewhere that's more reliable/remotely accessible, mostly to avoid the
> risk of me breaking them again when attempting to reconfigure bayfront.

That’s unfortunate.  Why is bayfront less reliable than we want it to
be?  Surely that’s not because it’s using Guix System, because
{berlin,ci}.guix.gnu.org also runs Guix System and has been reliably
hosting services for us.

I would not mind hosting services on one of the 30 new servers the MDC
bought for ci.guix.gnu.org, but I’d be happier if we figured out what’s
wrong with bayfront instead of centralizing all services in Berlin…

-- 
Ricardo

  reply	other threads:[~2020-02-17 20:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-17 13:47 Using the Hetzner Cloud Jonathan Brielmaier
2020-02-17 16:55 ` Ellen Papsch
2020-02-17 17:15   ` Alex Sassmannshausen
2020-02-18 11:44     ` Ellen Papsch
2020-02-18 11:58     ` Giovanni Biscuolo
2020-02-19 13:48       ` Alex Sassmannshausen
2020-02-21 18:00         ` Giovanni Biscuolo
2020-02-21 18:20           ` Alex Sassmannshausen
2020-02-18 17:38     ` Jonathan Brielmaier
2020-02-17 20:16   ` Christopher Baines
2020-02-18 17:35   ` Jonathan Brielmaier
2020-02-17 20:12 ` Christopher Baines
2020-02-17 20:39   ` Ricardo Wurmus [this message]
2020-02-17 21:28     ` Christopher Baines
2020-02-24 21:45   ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y2t1kkya.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=guix-europe@gnu.org \
    --cc=mail@cbaines.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.