You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Introduce Lix and make the shared configuration default to the upstream source-build path while still allowing consumers to opt out via `repo.lix.enable = false`.
Add flake input wiring for `lix` and `lix-module`, export the upstream default nixos and darwin modules, and apply the upstream source-build overlay during nixpkgs imports when Lix is enabled. Update the standalone Home Manager `nix.package` fallback so enabling Lix does not get overridden back to `pkgs.nix`, and regenerate `flake.nix` and `flake.lock` to capture the new inputs.
Refresh the README to document a Lix-first bootstrap flow for darwin and standalone Home Manager hosts, fix the concrete installer invocation, and tighten the domain-joined machine guidance around the known `sssd`/`nscd` workaround.
Strengthen repo and agent guidance to require staging new Nix files before validation, since untracked files are ignored by flake evaluation and can lead to misleading test results.
Add a temporary `just rebuild` workaround that appends `extra-deprecated-features = broken-string-indentation` to `NIX_CONFIG` so upstream zen-browser-flake warnings stay out of local rebuild output until 0xc000022070/zen-browser-flake#268 lands.
BREAKING CHANGE: Lix is now the default daemon and package-manager wiring for this repo's shared configuration surface. Consumers that need the previous behavior must opt out explicitly with `repo.lix.enable = false`.
Copy file name to clipboardExpand all lines: AGENTS.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -89,7 +89,7 @@ Use the Nix MCP first for Nix package, option, flake-input, and cache lookups be
89
89
- Make the smallest correct change.
90
90
- Prefer editing files under `modules/` and future `profiles/` trees over generated outputs.
91
91
- If a change affects generated flake output, regenerate `flake.nix` rather than hand-editing it.
92
-
- For any new file that must be evaluated by Nix, ensure it is tracked by git before relying on `nix` commands for validation; untracked files are ignored by flake evaluation.
92
+
- For any new file that must be evaluated by Nix, stage it with git before relying on `nix` commands for validation; untracked files are ignored by flake evaluation, and staged files are the safest default for accurate testing.
93
93
- Prefer exposing maintained operational commands via `nix run .#<name>` or `nix build .#<name>` instead of telling users to run repository-local shell scripts directly.
94
94
- Prefer introducing or consuming profiles instead of expanding repeated host import lists.
95
95
- Prefer mapping `hostFacts.roles` to existing profiles in `modules/roles/defaults.nix` rather than making hosts import repeated role bundles directly.
@@ -99,6 +99,7 @@ Use the Nix MCP first for Nix package, option, flake-input, and cache lookups be
99
99
## Verification
100
100
101
101
- For configuration changes, prefer the narrowest useful validation first.
102
+
- Before running validation for changes that add new Nix files or change generated flake inputs, stage the relevant new files first so evaluation sees the intended source tree.
102
103
- Use `nix flake check` when it meaningfully covers the change.
103
104
- Use `just rebuild` for local apply flows across nix-darwin, NixOS, and standalone Home Manager.
104
105
- On macOS bootstrap flows, preserving `NIX_CONFIG` may be required until managed Nix settings are active.
Copy file name to clipboardExpand all lines: README.md
+37-23Lines changed: 37 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,47 +24,61 @@ Reusable Nix library plus public live host configurations for NixOS, standalone
24
24
25
25
### Prerequisites
26
26
27
-
Install a standard multi-user Nix daemon. For nix-darwin hosts, prefer the standard Nix installer over Determinate if you want nix-darwin to manage the Nix installation.
27
+
For darwin and standalone Home Manager hosts, install a multi-user Nix daemon
28
+
manually to bootstrap the configuration. The recommended happy path is
29
+
[Lix](https://lix.systems/), which enables the required defaults out of the box.
28
30
29
-
On Arch Linux: `sudo pacman -S nix`
31
+
Our configuration relies on `flakes` and `nix-command`.
30
32
31
-
For other distros:
33
+
`trusted-users` should also cover your user directly or via an admin group,
34
+
especially for standalone Home Manager hosts where daemon settings are not
Copy file name to clipboardExpand all lines: modules/packages/dev/files/opencode/AGENTS.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,3 +15,4 @@ The `agent-health` skill must be active for any task longer than a few exchanges
15
15
- Prefer small verifiable steps over large monolithic outputs
16
16
- If a task is underspecified, ask one focused clarifying question before proceeding
17
17
- Escalate to the user rather than silently retrying when blocked
18
+
- Stage any new files that must participate in Nix evaluation before testing; untracked files are ignored by flake evaluation, so staging is required for reliable validation
0 commit comments