Bake in build toolchain + auto-run the Hermes installer on first boot
guest/common.nix was missing gcc/make/pkg-config/python3/xz, so the installer's node-pty compile step failed with "No C++ compiler found" - confirmed live during the hl-fwdesk incident. Also added systemd.services.hermes-install: runs the installer unattended (--non-interactive --skip-setup, confirmed supported via upstream's install.sh --help) as part of first boot, gated on its own .hermes-installed marker (same pattern as seedHermesState's .seeded). A real service rather than an activation script since it can take a while (compiling native modules) and shouldn't block boot or a nixos-rebuild. `hermes setup`/`hermes gateway install` stay manual - upstream docs don't show a non-interactive path for those, and they need real credentials anyway. Updated the README and the setup/migrate CLI's printed next-steps to match - two manual commands left instead of four. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
1 parent
67477953f1
commit
1239ea0148
3 files changed
+39
-7
No files matched your search
@@ -169,13 +169,22 @@ determinate-nixd login
|
||||
|
||||
# Pin the seeded flake
|
||||
sudo nix flake lock /etc/nixos
|
||||
```
|
||||
|
||||
# Install Hermes
|
||||
curl -fsSL https://raw.githubusercontent.com/NousResearch/hermes-agent/main/scripts/install.sh | bash
|
||||
The Hermes CLI installs itself automatically on first boot (`systemd.services.hermes-install`
|
||||
in `common.nix`) — it runs unattended, so there's nothing to run for that
|
||||
part. Give it a few minutes (it's compiling native Node modules); watch it
|
||||
with `journalctl --user -u hermes-install -f` if you want to see it happen.
|
||||
Once it's done:
|
||||
|
||||
```bash
|
||||
hermes setup
|
||||
hermes gateway install
|
||||
```
|
||||
|
||||
These two need real input (model provider, API keys, messaging platform
|
||||
tokens), so they stay manual.
|
||||
|
||||
The identity seed is already in place — `SOUL.md`, a starter `config.yaml`, a
|
||||
`USER.md` and a skill covering safe self-rebuilds. Back on the host, check
|
||||
the gateway came up and that the unit name matches the default:
|
||||
|
||||
Reference in new issue
Block a user