From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Sassmannshausen Subject: Re: =?utf-8?Q?=E2=80=9CTowards?= Guix for =?utf-8?Q?DevOps?= =?utf-8?Q?=E2=80=9D?= Date: Fri, 26 Jul 2019 10:10:25 +0100 Message-ID: <87imrp40vy.fsf@gmail.com> References: <871ryvgow6.fsf@gnu.org> Reply-To: alex.sassmannshausen@gmail.com Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:57429) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hqwFL-0003c3-Os for guix-devel@gnu.org; Fri, 26 Jul 2019 05:10:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hqwFF-0001Li-Ff for guix-devel@gnu.org; Fri, 26 Jul 2019 05:10:37 -0400 Received: from mail-wm1-x32f.google.com ([2a00:1450:4864:20::32f]:51652) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hqwFF-00014X-5y for guix-devel@gnu.org; Fri, 26 Jul 2019 05:10:33 -0400 Received: by mail-wm1-x32f.google.com with SMTP id 207so47358785wma.1 for ; Fri, 26 Jul 2019 02:10:29 -0700 (PDT) Received: from watership (cpc116648-aztw31-2-0-cust127.18-1.cable.virginm.net. [81.111.22.128]) by smtp.gmail.com with ESMTPSA id h1sm37990873wrt.20.2019.07.26.02.10.26 for (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Fri, 26 Jul 2019 02:10:27 -0700 (PDT) In-reply-to: <871ryvgow6.fsf@gnu.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: guix-devel@gnu.org Hello, I just wanted to drop a quick note on the guix deploy work carried out by Jakob. I've started using it to manage servers, and it seems to work an absolute charm. Congratulations to all involved. I did hit the following small stumbling blocks: - When first running guix deploy it complained about a missing /etc/guix/signing-key.sec. I fairly quickly realised that deploy probably used archive infrastructure, so figured out how to generate the keys. But maybe the manual should contain a line about this? - The machine-ssh-configuration allows for the specification of users other than root, but my understanding is that only root will allow for a successful deployment (because root is required to actually reconfigure the target system). I don't know what conclusions to draw from this, as I'm not 100% on the roadmap for development. But maybe for now, this could be a gotcha for new users. Best wishes, Alex Ludovic Court=C3=A8s writes: > Hello Guix! > > Jakob wrote a lovely post about the ongoing work implementing =E2=80=98gu= ix > deploy=E2=80=99 as part of GSoC: > > https://gnu.org/s/guix/blog/2019/towards-guix-for-devops/ > > Check it out! > > Ludo=E2=80=99.