From: Giovanni Biscuolo <g@xelera.eu>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: how to split config.scm in multiple files
Date: Tue, 27 Nov 2018 18:57:08 +0100 [thread overview]
Message-ID: <87in0ixv2j.fsf@roquette.mug.biscuolo.net> (raw)
In-Reply-To: <87pnuxb6ws.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1176 bytes --]
Hi Ludo,
ludo@gnu.org (Ludovic Courtès) writes:
[...]
> The ‘include’ form exists but you would need to use it at the top
> level.
OK, got it thanks!
> However, I recommend using Guile’s module system instead. An example of
> that can be found here:
>
> • modules:
> https://git.savannah.gnu.org/cgit/guix/maintenance.git/tree/hydra/modules/sysadmin
ooooh: maintenance.git is *almost* more interesting than the guix manual
itself :-O
> • config files that use these modules:
> https://git.savannah.gnu.org/cgit/guix/maintenance.git/tree/hydra/berlin.scm
> https://git.savannah.gnu.org/cgit/guix/maintenance.git/tree/hydra/build-machine.scm
OK I'm still not able to hack my modules in Guile but that code is clear enough
for me to understand how it works... and it's great! (\me study!)
IaGC [1] is much more... *functional* than other forms of IaC :-)
> Here, assuming you’re in the hydra/ directory, you’d simply run, say:
>
> guix system reconfigure -L ./modules ./berlin.scm
got it!
kudos!
Giovanni
[1] Infrastructure as Guile Code
--
Giovanni Biscuolo
Xelera IT Infrastructures
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-11-27 17:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-17 8:59 how to split config.scm in multiple files Giovanni Biscuolo
2018-11-17 9:16 ` Julien Lepiller
2018-11-22 13:04 ` Ludovic Courtès
2018-11-27 17:57 ` Giovanni Biscuolo [this message]
2018-11-28 17:11 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87in0ixv2j.fsf@roquette.mug.biscuolo.net \
--to=g@xelera.eu \
--cc=help-guix@gnu.org \
--cc=ludo@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.