fix(distant-shore): build on sunken-ship (avoids self-SSH on closure copy) 🔧
This commit is contained in:
parent
df18b1cfaf
commit
0cdb4b8697
1 changed files with 4 additions and 2 deletions
|
|
@ -172,13 +172,15 @@ in {
|
||||||
# distant-shore — ThinkPad X13 Gen 2, WiFi, Secure Boot via shim+MOK
|
# distant-shore — ThinkPad X13 Gen 2, WiFi, Secure Boot via shim+MOK
|
||||||
# (installed standalone, then migrated into clan). targetHost is the LAN
|
# (installed standalone, then migrated into clan). targetHost is the LAN
|
||||||
# IP for the first `clan machines update`; switch to its ZT IPv6 once the
|
# IP for the first `clan machines update`; switch to its ZT IPv6 once the
|
||||||
# mesh is up. Builds on the box itself (it has nix + internet).
|
# mesh is up. buildHost = sunken-ship: it's an x86_64 builder whose key is
|
||||||
|
# already in distant-shore's authorized_keys, so the closure copy works
|
||||||
|
# (building on distant-shore itself needs a fragile self-SSH).
|
||||||
machines.distant-shore = {
|
machines.distant-shore = {
|
||||||
imports = [
|
imports = [
|
||||||
{
|
{
|
||||||
clan.core.enableRecommendedDefaults = false;
|
clan.core.enableRecommendedDefaults = false;
|
||||||
clan.core.networking.targetHost = "danny@192.168.1.182";
|
clan.core.networking.targetHost = "danny@192.168.1.182";
|
||||||
clan.core.networking.buildHost = "danny@192.168.1.182";
|
clan.core.networking.buildHost = "danny@sunken-ship";
|
||||||
}
|
}
|
||||||
clanHostsModule
|
clanHostsModule
|
||||||
../nixos/hosts/distant-shore.nix
|
../nixos/hosts/distant-shore.nix
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue