From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Maxim Cournoyer <maxim.cournoyer@gmail.com>,
Felix Lechner <felix.lechner@lease-up.com>,
guix-devel@gnu.org
Subject: Re: Better support remote deployment
Date: Sun, 10 Dec 2023 14:49:27 +0100 [thread overview]
Message-ID: <87v896i2s6.fsf@elephly.net> (raw)
In-Reply-To: <87y1exu3hn.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> That said, I wonder if this would really be more convenient than SSH’ing
> into the target machine and running the commands right there. Perhaps
> I’m missing something about the use case?
The use case is to have a development host where packages are built and
then pushed / installed on a remote that lacks the prerequisites to
build the packages (e.g. checkout of development source repositories).
I feel it would be a good fit for “guix deploy”, which has a similar set
of assumptions but for deploying Guix System rather than mere package
profiles.
--
Ricardo
prev parent reply other threads:[~2023-12-10 13:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 12:19 Better support remote deployment Ricardo Wurmus
2023-11-01 15:20 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-11-02 9:59 ` Ricardo Wurmus
2023-11-07 19:07 ` Maxim Cournoyer
2023-11-07 19:45 ` Ricardo Wurmus
2023-11-08 2:12 ` Maxim Cournoyer
2023-11-08 2:39 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-11-08 14:36 ` Maxim Cournoyer
2023-11-09 7:38 ` Efraim Flashner
2023-11-09 15:01 ` Maxim Cournoyer
2023-11-16 15:23 ` Ludovic Courtès
2023-11-16 16:47 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-11-21 1:33 ` Tomas Volf
2023-11-23 4:24 ` Maxim Cournoyer
2023-12-10 13:49 ` Ricardo Wurmus [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=87v896i2s6.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=felix.lechner@lease-up.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=maxim.cournoyer@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).