1.6 KiB
1.6 KiB
robotnix — adapter for the robotnix flake
robotnix (self-managed NixOS systemd-nspawn robots) lives in its own repo:
git+ssh://gitea@gitea.app.internal:22/ari/robotnix.git, a flake input of
this repo. Its README and docs/ describe the design, options, CLI and
tests. Hosts configure it under services.robotnix (like services.hermenix).
This folder only holds default.nix, which:
- imports
robotnix.nixosModules.default(passed in viaspecialArgs); - defaults
user,authorizedKeys,dnsUpstreamsandlocalDomainsfrom theskyguser, the SSH master keys and the internal networking map; - asserts no robot address clashes with an app in
skyg.internalNetworkingMap.apps.
Decisions
- Own repo (2026-10): robotnix moved out of
modules/nixos/serverso it can grow (storage backends, Genix, child robots) with its own tests. - Namespace:
services.robotnix, notskyg.*, same exception as hermenix: the options belong to an external flake. - hermes-agent pin: the input follows this repo's
hermes-agent, so robots pin the same revision the host locked. - Buzz stays here: robotnix knows nothing about Buzz. A robot's seed
config (e.g.
hosts/hl-fwdesk/services/robotnix/sibli.nix) buildspkgs/buzz-clifrom this repo and setsBUZZ_CLI_PATHitself. That relative path works for the seed build only, which is fine for ephemeral robots; a persistent robot that rebuilds itself would need its own copy. - nspawn, not
oci-containers: the oci-containers rule targets Docker/Podman. nspawn robots need their own store for self-rebuilds, which thecontainers.*module can't give.