From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Felix Lechner <felix.lechner@lease-up.com>,
Ricardo Wurmus <rekado@elephly.net>,
guix-devel@gnu.org
Subject: Re: Better support remote deployment
Date: Wed, 22 Nov 2023 23:24:22 -0500 [thread overview]
Message-ID: <87edgh85c9.fsf@gmail.com> (raw)
In-Reply-To: <ZVwI-QXfBq--AzYu@ws> (Tomas Volf's message of "Tue, 21 Nov 2023 02:33:45 +0100")
Hi,
Tomas Volf <~@wolfsden.cz> writes:
[...]
> I was following the debate, but maybe I have missed something, so I will put
> forward my use case as well. I have two properties I would like to have from a
> "remote deploy" mechanism, and they are not satisfied by SSH-ing to the machine
> and running the commands there.
>
> 1. No need for `guix pull'. I run (a little) custom Guix, so running `guix
> pull' is somewhat expensive. I do not want to do it just to deploy something
> (be it a system, or home, or profile).
>
> 2. No need to copy over the definitions. My configurations are part of a git
> repository, which I would like to keep local to just my development machine. So
> rsync-ing it over to the remote machine in order to run command there is
> something I would like to avoid.
>
> If, however, I can build a profile locally, `guix copy' it over, and *then* SSH
> into the machine and somehow activate the profile (be it home or regular
> profile), that would work for me. Is that currently possible?
That's possible if the remote machine runs Guix System and you use 'guix
deploy'. Otherwise, if the remote machine is a foreign distribution,
you'd have to manually copy things with 'guix copy', like Ricardo has
been doing and wanting to improve here.
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-11-23 4:25 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 [this message]
2023-12-10 13:49 ` Ricardo Wurmus
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=87edgh85c9.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=felix.lechner@lease-up.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=rekado@elephly.net \
/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.