From: "Thompson, David" <dthompson2@worcester.edu>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: “Managing Servers with GNU Guix: A Tutorial”
Date: Tue, 5 Nov 2019 09:04:53 -0500 [thread overview]
Message-ID: <CAJ=Rwfa=S=nwydmvmhQtk81mUPAp-0nucjqqqnKc1Sb7vqoOLA@mail.gmail.com> (raw)
In-Reply-To: <17cd56cf-357a-735b-e412-1920fce085d6@crazy-compilers.com>
Hi Hartmut,
On Tue, Nov 5, 2019 at 3:09 AM Hartmut Goebel
<h.goebel@crazy-compilers.com> wrote:
>
> Am 04.11.19 um 15:36 schrieb Ludovic Courtès:
> > Jakob wrote a great tutorial on how to use ‘guix deploy’ to deploy Guix
> > System to one machine or to several virtual private servers (VPSs):
> >
> > https://guix.gnu.org/blog/2019/managing-servers-with-gnu-guix-a-tutorial/
>
> Great tutorial! Thanks.
>
> On questions: For the first example: Does guix installed on the manged
> host need to be up-todate? Or will the update be done as part of the
> "operating system closure", which is send to the managed host?
>
> I spotted a minor error/typo, which is a tiny bit confusing for newbies:
> In the first example it reads "|(define os …" whereas in the text below
> "%system" is referenced. (Also ||"/home/alyssa/.ssh/server_key" is a bit
> misleading. I suggest "…/key-for-server")|
Thanks for catching those issues that I missed while editing. I'll try
to fix them today!
- Dave
prev parent reply other threads:[~2019-11-05 14:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 14:36 “Managing Servers with GNU Guix: A Tutorial” Ludovic Courtès
2019-11-05 8:09 ` Hartmut Goebel
2019-11-05 14:04 ` Thompson, David [this message]
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='CAJ=Rwfa=S=nwydmvmhQtk81mUPAp-0nucjqqqnKc1Sb7vqoOLA@mail.gmail.com' \
--to=dthompson2@worcester.edu \
--cc=h.goebel@crazy-compilers.com \
--cc=help-guix@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.
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).