fix(machines/build01): move back to stc-ng
In some distant past, stc-ng had some clear troubles while deploying the machine when we were bootstrapping infra. This was fixed by rolling back to the old stc. Having retried right now, stc-ng seems to transition the new system correctly, so let's switch to it for the time being. Change-Id: I99f92618841b49357a28212955b62bf5e495e761 Signed-off-by: Raito Bezarius <raito@lix.systems> Reviewed-on: https://cl.snix.dev/c/snix/+/30503 Tested-by: besadii Reviewed-by: Florian Klink <flokli@flokli.de>
This commit is contained in:
parent
e285cbe8cf
commit
5d16817f80
1 changed files with 0 additions and 1 deletions
|
|
@ -35,7 +35,6 @@ in
|
||||||
};
|
};
|
||||||
|
|
||||||
boot.loader.initScript.enable = true;
|
boot.loader.initScript.enable = true;
|
||||||
system.switch.enableNg = false;
|
|
||||||
nix.nrBuildUsers = 256;
|
nix.nrBuildUsers = 256;
|
||||||
nix.settings.max-jobs = 64;
|
nix.settings.max-jobs = 64;
|
||||||
nix.gc.automatic = true;
|
nix.gc.automatic = true;
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue