Rename project to hermenix; convert host scripts to a Nu CLI

services.hermesVm -> services.hermenix throughout. setup.sh and
migrate-docker-hermes.sh are replaced by nu/hermenix.nu (setup + migrate
subcommands), packaged as a flake output (packages.${system}.hermenix,
pkgs.writers.writeNuBin) so it's installable without cloning conventions
beyond the repo itself. Both subcommands verified end-to-end against a
sandboxed dry run (stubbed disk/cache tools, a local ssh stand-in for the
migrate path) before landing.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
ariandClaude Sonnet 5 committed 2026-09-15 13:26:18 -04:00
1 parent 12227460fd
commit 2b33b98bae
10 files changed
+570 -568

No files matched your search

+1 -1
View File
@@ -1,7 +1,7 @@
{ config, lib, pkgs, ... }:
let
# These must match services.hermesVm.* on the host. If you changed the
# These must match services.hermenix.* on the host. If you changed the
# defaults there, change them here too before building the image.
hostAddress = "10.77.0.1";
guestAddress = "10.77.0.2";
@@ -52,6 +52,6 @@ networking.firewall.allowedTCPPorts = [ 22 8080 ];
```
Reaching further — a LAN device, another host, or being reachable from
outside — needs an operator-side change to `services.hermesVm.*`
outside — needs an operator-side change to `services.hermenix.*`
(`lanAccess`, `hostAccess`, `publish`). You cannot grant yourself that from
in here, on purpose. Ask rather than looking for a way around it.