Re: Better support remote deployment

[Maxim Cournoyer]

Hi,

Efraim Flashner <efraim@flashner.co.il> writes:

[...]

>> '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.

That's some idea I suggested earlier (add integration form 'guix home'
configs to an operating system definition).  That has merit on its own,
but wouldn't solve Ricardo's use case, which is to deploy a profile on a
*foreign* distribution (not Guix System).

-- 
Thanks,
Maxim