From: Ellen Papsch <ellen.papsch@wine-logistix.de>
To: alex.sassmannshausen@gmail.com, guix-devel@gnu.org
Subject: Re: Using the Hetzner Cloud
Date: Tue, 18 Feb 2020 12:44:40 +0100 [thread overview]
Message-ID: <17c4238f369c939c5787b41c6491abdc0c669b3c.camel@wine-logistix.de> (raw)
In-Reply-To: <87mu9hnniw.fsf@gmail.com>
Am Montag, den 17.02.2020, 18:15 +0100 schrieb Alex Sassmannshausen:
>
>
> So I deploy debian, then copy across a script and run that. This
> takes
> care of turning the debian machine into a guix machine and deploys my
> sys config immediately.
>
> This is by far the fastest way of deploying to Hetzner VMs I've found
> yet.
>
> It also means you can use Hetzner's CLI for creating and managing
> your
> VMs.
That sounds nice. I had wondered if there's some sort of FrankenDebian
way but did not pursue it. Given this line in the script:
mv var/guix /var/ && mv gnu /
there seems to be a complete takeover, even better than a FrankenDebian
:-)
> It's on my to do list to create a solid guix deploy server creation
> module for guix.
That would certainly be appreciated.
I'm currently in the process of cementing Guix usage here (for
databases at least). If I succeed and get some time, I might be able to
do a first stab. Though it would be more useful for applications, which
come and go more often than databases. We currently manage apps with
ansible, I already have started lobbying at low rate. But first things
first -- databases!
Best regards
next prev parent reply other threads:[~2020-02-18 11:44 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 [this message]
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
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=17c4238f369c939c5787b41c6491abdc0c669b3c.camel@wine-logistix.de \
--to=ellen.papsch@wine-logistix.de \
--cc=alex.sassmannshausen@gmail.com \
--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 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.