From: Tomas Volf <~@wolfsden.cz>
To: "Simen Endsjø" <contact@simendsjo.me>
Cc: help-guix@gnu.org
Subject: Re: Not sure how to add an offload server
Date: Thu, 07 Nov 2024 00:49:03 +0100 [thread overview]
Message-ID: <87bjyrc49c.fsf@wolfsden.cz> (raw)
In-Reply-To: <bf36a9f9-9a5b-480c-b721-e0858855425b@app.fastmail.com> ("Simen Endsjø"'s message of "Wed, 06 Nov 2024 22:20:39 +0100")
[-- Attachment #1: Type: text/plain, Size: 1496 bytes --]
Simen Endsjø <contact@simendsjo.me> writes:
> I don't understand how /etc/guix and /usr/local/etc/guix fits together.
> /usr/local/etc/guix/acl does not contain the public key, but it exists
> and symlinks to a store item.
They should not fit together, /usr/local does not exist at all on my
GuixSD system.
> Could someone link me to a working offload setup?
These two blocks are all I need.
--8<---------------cut here---------------start------------->8---
(define %build-machines
(list #~(build-machine
(name "some-server")
(systems (list "x86_64-linux" "i686-linux" "aarch64-linux"))
(host-key "some-host-key")
(user "build-offload")
(parallel-builds 4)
(overload-threshold #f)
(private-key "/some/key"))))
--8<---------------cut here---------------end--------------->8---
--8<---------------cut here---------------start------------->8---
(simple-service 'offload guix-service-type
(guix-extension
(build-machines %build-machines)))
--8<---------------cut here---------------end--------------->8---
(Well, I also needed to authorized the keys using `guix archive', as the
manual instructs. And create the `build-offload' user on the server
with allowed login by ssh key.)
T.
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 853 bytes --]
next prev parent reply other threads:[~2024-11-06 23:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-02 22:13 Not sure how to add an offload server Simen Endsjø
2024-11-03 14:06 ` Tomas Volf
2024-11-03 15:05 ` Simen Endsjø
2024-11-06 21:20 ` Simen Endsjø
2024-11-06 23:49 ` Tomas Volf [this message]
2024-11-07 8:03 ` Simen Endsjø
2024-11-07 9:06 ` Hilton Chain
2024-11-07 11:17 ` Simen Endsjø
2024-11-07 14:35 ` Felix Lechner via
2024-11-07 21:17 ` Simen Endsjø
2024-11-07 21:51 ` Simen Endsjø
2024-11-07 21:59 ` Simen Endsjø
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=87bjyrc49c.fsf@wolfsden.cz \
--to=~@wolfsden.cz \
--cc=contact@simendsjo.me \
--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).