From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:470:142:3::10]:56411)
 by lists.gnu.org with esmtp (Exim 4.86_2)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1hjJbX-0002Jf-PY
 for guix-patches@gnu.org; Fri, 05 Jul 2019 04:30:04 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1hjJbW-0004EA-R3
 for guix-patches@gnu.org; Fri, 05 Jul 2019 04:30:03 -0400
Received: from debbugs.gnu.org ([209.51.188.43]:43515)
 by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
 (Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
 id 1hjJbW-0004DZ-NH
 for guix-patches@gnu.org; Fri, 05 Jul 2019 04:30:02 -0400
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1hjJbW-0004QP-G0
 for guix-patches@gnu.org; Fri, 05 Jul 2019 04:30:02 -0400
Subject: [bug#36404] [PATCH v4 4/4] doc: Add section for 'guix deploy'.
Resent-Message-ID: <handler.36404.B36404.156231535916933@debbugs.gnu.org>
From: Ludovic =?UTF-8?Q?Court=C3=A8s?= <ludo@gnu.org>
References: <87o92ianbj.fsf@sdf.lonestar.org> <87o92glap5.fsf@dustycloud.org>
 <878sthoqzi.fsf@gnu.org> <87imsl9tsx.fsf_-_@sdf.lonestar.org>
 <87ef399tpu.fsf_-_@sdf.lonestar.org>
 <87a7dx9tog.fsf_-_@sdf.lonestar.org>
 <875zol9tn2.fsf_-_@sdf.lonestar.org>
 <871rz99tl9.fsf_-_@sdf.lonestar.org> <875zoldqah.fsf@kyleam.com>
 <87muhwtmfp.fsf@sdf.lonestar.org> <871rz874l2.fsf@kyleam.com>
 <877e90tj7l.fsf_-_@sdf.lonestar.org>
 <8736jotj5v.fsf_-_@sdf.lonestar.org>
 <87y31gs4k5.fsf_-_@sdf.lonestar.org>
 <87tvc4s4iv.fsf_-_@sdf.lonestar.org>
 <87muhws4hd.fsf_-_@sdf.lonestar.org>
Date: Fri, 05 Jul 2019 10:29:06 +0200
In-Reply-To: <87muhws4hd.fsf_-_@sdf.lonestar.org> (Jakob L. Kreuze's message
 of "Tue, 02 Jul 2019 13:58:38 -0400")
Message-ID: <87lfxcnaul.fsf@gnu.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
List-Id: <guix-patches.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-patches>,
 <mailto:guix-patches-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/guix-patches>
List-Post: <mailto:guix-patches@gnu.org>
List-Help: <mailto:guix-patches-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-patches>,
 <mailto:guix-patches-request@gnu.org?subject=subscribe>
Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org
Sender: "Guix-patches" <guix-patches-bounces+kyle=kyleam.com@gnu.org>
To: "Jakob L. Kreuze" <zerodaysfordays@sdf.lonestar.org>
Cc: 36404@debbugs.gnu.org

zerodaysfordays@sdf.lonestar.org (Jakob L. Kreuze) skribis:

> * doc/guix.texi: Add section "Invoking guix deploy".

Yay!

You can add a copyright line for you at the top of guix.texi.

> +@section Invoking @code{guix deploy}
> +
> +We've already seen @code{operating-system} declarations used to manage a
> +machine's configuration locally.  Suppose you need to configure multiple
> +machines, though---perhaps you're managing a service on the web that's
> +comprised of several servers.  @command{guix deploy} enables you to use =
those
> +same @code{operating-system} declarations to manage multiple remote host=
s at
> +once as a logical ``deployment''.

Perhaps add something like:

  @quotation Note
  The functionality described in this section is still under development
  and is subject to change.  Get in touch with us on
  @email{guix-devel@@gnu.org}!
  @end quotation

That way, if we make a Guix release before this is all stabilized,
we make sure people have appropriate expectations.  :-)

> +complex deployment may involve, for example, starting virtual machines t=
hrough
> +a VPS provider.  In such a case, a different @var{environment} type woul=
d be
     ^^^
I would write =E2=80=9CVirtual Private Server (VPS)=E2=80=9D.

I hope the nitpicking level is acceptable, let me know.  I=E2=80=99m really
excited to see this land in master!

Ludo=E2=80=99.