unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Christine Lemmer-Webber <cwebber@dustycloud.org>
To: help-guix@gnu.org
Subject: Ad-hoc offloading to a server
Date: Mon, 20 Sep 2021 14:25:11 -0400	[thread overview]
Message-ID: <87mto75cb6.fsf@dustycloud.org> (raw)

Sometimes I've wanted to offload builds ad-hoc to another server, like
so:

  guix build mypackage --offload-to=cwebber@beefybuilder.org

This would offload by ssh'ing into that server and doing the offloading
there, but it's a more explicit user specified location.

Thoughts?  Would this be a worthwhile feature?

 - Christine

PS: I suppose despite being a more explicit operation, I suppose the
/etc/guix/acl file can't be avoided under our current security model,
because we're still trusting that the remote location is trustworthy
enough to put this build result in our store as the result associated
with this input.  One user could, otherwise, screw over all others.


             reply	other threads:[~2021-09-20 18:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-20 18:25 Christine Lemmer-Webber [this message]
2021-09-20 19:38 ` Ad-hoc offloading to a server 'edk@beaver-labs.com'

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=87mto75cb6.fsf@dustycloud.org \
    --to=cwebber@dustycloud.org \
    --cc=help-guix@gnu.org \
    /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).