unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Gábor Boskovits" <boskovits@gmail.com>
To: jimmy@thrasibule.mx
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Automated system upgrade
Date: Mon, 3 Feb 2020 19:16:17 +0100	[thread overview]
Message-ID: <CAE4v=pjbLsVdy6Uk-Cs0J0TmY7135X2spmb-C8Kh5K1amFPCzQ@mail.gmail.com> (raw)
In-Reply-To: <CAMqSRmBwm1QsjCpu9vaH_PirXBytZHvurbRJ3weY+31wx3nxag@mail.gmail.com>

Hello,

Jimmy Thrasibule <jimmy.thrasibule@gmail.com> ezt írta (időpont: 2020.
febr. 3., H, 13:37):
>
> Hi,
>
> I would like to know about the best way one would automate a Guix system
> reconfiguration. The idea is to put the system configuration stanza into a
> Git repository and then having the systems regularly pull from this
> repository and reconfigure.
>
> The way I see it so far would take the following steps:
>
> 1. Create a Guix package with all the system configuration (the package can
> call guix system reconfigure after install).
> 2. Create a Guix pull channel.
> 3. Have the system automatically pulling the latest revision. (??)
> 4. Repeat.
>

There is no need for 1 and 2.

> Does this plan is looking sane to you and how can I regularly pull the
> system's repository? Maybe using a service or a cron job?

You should create a service which updates a repo from the cron job and
then reconfigure.

There is something like this on berlin, you can have a look at the config
in the maintenance repository. Look for static-website-service. Hope
this helps.

>
> Regards,
> Jimmy


Best regards,
g_bor
-- 
OpenPGP Key Fingerprint: 7988:3B9F:7D6A:4DBF:3719:0367:2506:A96C:CF63:0B21

  reply	other threads:[~2020-02-03 18:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-03 12:36 Automated system upgrade Jimmy Thrasibule
2020-02-03 18:16 ` Gábor Boskovits [this message]
2020-02-03 19:02   ` sirgazil

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='CAE4v=pjbLsVdy6Uk-Cs0J0TmY7135X2spmb-C8Kh5K1amFPCzQ@mail.gmail.com' \
    --to=boskovits@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=jimmy@thrasibule.mx \
    /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).