fixing vm issues
This commit is contained in:
1 parent
49c6d6e6cc
commit
0e76632d2e
9 files changed
+138
-10
No files matched your search
+3
-3
@@ -29,7 +29,7 @@ Only after the user approves the plan may you proceed with edits.
|
||||
**DO NOT RUN ANY OF THESE COMMANDS AT ANY TIME, FOR ANY REASON:**
|
||||
|
||||
```
|
||||
nix build
|
||||
nix build # unless it's to test the vm via 'bin/runvmtest'
|
||||
nix flake check
|
||||
hermenix setup # unless the user is actively running it themselves with you watching
|
||||
hermenix migrate # same — it writes into a live guest
|
||||
@@ -95,9 +95,9 @@ These are always safe to perform without asking:
|
||||
|
||||
- Reading any file in this repo
|
||||
- Editing `modules/host.nix` to add/adjust options (gated behind `mkIf
|
||||
cfg.enable`, following the existing style)
|
||||
cfg.enable`, following the existing style)
|
||||
- Editing `nu/hermenix.nu` — check any change by parsing it (`nu
|
||||
nu/hermenix.nu --help` and `nu nu/hermenix.nu <subcommand> --help` parse
|
||||
nu/hermenix.nu --help` and `nu nu/hermenix.nu <subcommand> --help` parse
|
||||
the whole file without running any subcommand body) before handing it back
|
||||
- Editing `guest/hermes/home` / `guest/hermes/workspace` template seed content
|
||||
(as long as it stays free of real secrets — see above)
|
||||
|
||||
Reference in new issue
Block a user