unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Tim Lee <progscriptclone@gmail.com>
To: ilmu@rishi.is
Cc: help-guix@gnu.org
Subject: Re: Something like nixos-infect?
Date: Sat, 27 Mar 2021 05:41:21 +0800	[thread overview]
Message-ID: <20210326214121.regyf23t7fjhfbrr@home-guest> (raw)
In-Reply-To: <d__JDIG-tQmUt-zp7A8GgHBHwNSuQBK-xU_abtwaNewa13sprQGx_IRSuwwFPBlDGMWHFK2mC9LcqY1DHW3aZDWXuJ_o-nBea011c1pxBI0=@rishi.is>

> Something like nixos-infect?

It looks like there is something named "guix-infect":
https://github.com/guix-mirror/guix/blob/v1.2.0/gnu/machine/digital-ocean.scm#L191

Perhaps the blog article about 'guix deploy' would help you:
https://guix.gnu.org/blog/2019/managing-servers-with-gnu-guix-a-tutorial/

I think nix-infect will become less relevant in the future because
nixos-generators (https://github.com/nix-community/nixos-generators) is
able to generate custom images for many cloud service providers. Instead
of overwriting an exiting system with NixOS, the custom images boot
directly into NixOS.

It seems that something like nixos-generators is possible in Guix:
* "Hosting a blog using only Scheme"
  (https://othacehe.org/hosting-a-blog-using-only-scheme.html)
* "Re: Easy DigitalOcean setup?"
  (https://lists.gnu.org/archive/html/help-guix/2020-11/msg00053.html)
  See the attached do-conf.scm file in that reply.

It seems that Guix suffers from the lack of documentation in this area
(installing and deploying on the cloud).


      parent reply	other threads:[~2021-03-26 22:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-26 18:10 Something like nixos-infect? ilmu
2021-03-26 21:23 ` Vincent Legoll
2021-03-26 21:29   ` Vincent Legoll
2021-03-26 21:41 ` Tim Lee [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=20210326214121.regyf23t7fjhfbrr@home-guest \
    --to=progscriptclone@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=ilmu@rishi.is \
    /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).