On Wed, Nov 08, 2023 at 09:36:46AM -0500, Maxim Cournoyer wrote:
> Hello,
> 
> Felix Lechner <felix.lechner@lease-up.com> writes:
> 
> > Hi,
> >
> > On Tue, Nov 07 2023, Maxim Cournoyer wrote:
> >
> >> Then your suggestion to extend 'guix package' to be able to
> >> install a profile from a store profile sounds useful, or perhaps a new
> >> 'guix deploy-profile' (or a better name / sub-command?) that would
> >> automate the copy and installation in one step.
> >
> > We have a lot of sub-commands already. Could 'guix deploy' instead be
> > fed something other than a 'machine' record?
> 
> Perhaps too much of an overload of that command; not sure.
> 
> > How about a 'remote-user-profile'?
> 
> 'guix package' is already the command we use to create profiles; maybe
> it could accept a '--remote' argument to operate on a remote machine?
> Or is this not what 'GUIX_DAEMON_SOCKET=ssh://your-target guix package
> -m manifest.scm' can already accomplish? :-)

Currently there's no ssh connection caching, so using GUIX_DAEMON_SOCKET
can be quite slow, I normally allow 5-10 minutes for a profile. That
works best when you can't use guix copy to send derivations over.

The profile effectively already exists, it doesn't need to be computed
on each machine.  It does seem more like deploy: take this profile, send
it to that machine, and activate it there.  `guix deploy` already takes
a file, the file could have a profile (or home config?) and a location
for the profile. And a user.

-- 
Efraim Flashner   <efraim@flashner.co.il>   רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted