From: Carlo Zancanaro <carlo@zancanaro.id.au>
To: Nicolas Odermatt-Lemay <nodermattlemay@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Efficient iterative shepherd service development ?
Date: Wed, 07 Aug 2024 19:05:01 +1000 [thread overview]
Message-ID: <87v80c9002.fsf@zancanaro.id.au> (raw)
In-Reply-To: <CAC-BrWpGxeQJpRSCT3nqn=Z-whjcG+fu1bs7JpzdJod=ELv_zw@mail.gmail.com> (Nicolas Odermatt-Lemay's message of "Mon, 5 Aug 2024 00:06:39 -0400")
On Mon, Aug 05 2024, Nicolas Odermatt-Lemay wrote:
> Would this be a way to go ? If it is, how could this be implemented ?
> And do you have any other advice ?
When I work on services I usually use "guix system vm" and/or "guix
system container". These allow me to instantiate a system with the
service(s) that I'm working on without risking breaking my real system.
It also makes cleaning up between tests much simpler: I just kill the
VM/container.
I find it easier to write a minimal operating-system definition, rather
than using one of my real system definitions, but you can do it either
way.
Carlo
prev parent reply other threads:[~2024-08-07 9:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 4:06 Efficient iterative shepherd service development ? Nicolas Odermatt-Lemay
2024-08-05 18:36 ` Felix Lechner via
2024-08-07 9:05 ` Carlo Zancanaro [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=87v80c9002.fsf@zancanaro.id.au \
--to=carlo@zancanaro.id.au \
--cc=help-guix@gnu.org \
--cc=nodermattlemay@gmail.com \
/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).