This repository has no description
4.3 kB
111 lines
1# CLAUDE.md
2
3This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
4
5## Repository Overview
6
7This is lassulus's personal NixOS/nix-darwin configuration repository, built on clan-core for managing multiple machines. It includes:
8- Multiple machine configurations in `machines/`
9- Configuration modules in `configs/` and `modules/`
10- Custom packages in `pkgs/`
11- packages which could in theory be upstreamed to nixkgs should go into the pkgs folder, in the tools folder we add tools we write ourself which are more complex or not upstreamable
12
13## Key Architecture Components
14
15### Machine Management
16- **Clan-core**: Primary framework for managing multiple machines
17- **Secrets**: Uses password-store for secrets management via clan.core.vars
18
19### Network Overlays
20The repository manages multiple overlay networks:
21- **Tor**: Anonymous network access
22
23### Module System
24- `configs/`: Main configuration modules
25- `configs/default.nix`: imported by all machines
26- `modules/`: Custom NixOS module definitions
27- Stockholm modules are also imported for krebs infrastructure
28
29## Common Development Commands
30
31```bash
32# Enter development shell
33nix develop
34
35# Deploy a NixOS machine (tools/deploy): one Secure Enclave unlock for all
36# secrets, builds on the target, shows source/closure diff, asks before
37# switching. `s` runs apps from ~/src/superconfig, so pass --flake to deploy
38# a different checkout/worktree. NEVER use `clan machines update`: it
39# decrypts each secret separately and fails on the Secure Enclave prompt.
40s deploy --flake . <MACHINE_NAME>
41
42# Agents: deploy only when the user asked for it, and then always with
43# --yes. Without it the run stops at the [y/N] switch prompt (and the source
44# diff can wait in a pager) and looks hung. --yes skips both; the diffs are
45# still printed, so read them in the output afterwards.
46s deploy --flake . --yes <MACHINE_NAME>
47
48# Format code
49nix fmt
50
51# Build NixOS configuration
52nix build .#nixosConfigurations.<machine-name>.config.system.build.toplevel
53
54# Build Darwin configuration
55nix build .#darwinConfigurations.barnacle.system
56
57# Deploy/rebuild Darwin configuration (for barnacle)
58sudo darwin-rebuild switch --flake .#barnacle
59
60# Access machines via SSH (as root, see below)
61ssh root@<machine-name>.r # via retiolum
62ssh root@<machine-name>.s # via spora
63ssh root@<machine-name>.n # via nether
64torify ssh root@$(pass show machines/<machine-name>/tor-hostname) # via tor
65```
66
67## Remote Machine Access
68
69**CRITICAL**: For privileged work on a remote machine (firewall rules,
70journals of system services, systemctl, reading /run/secrets, ...), ssh in as
71root (`ssh root@<machine>.r`). NEVER use `sudo` on remote systems. Ssh as the
72normal user (`lass@`) only to act as that user, e.g. to run user tools.
73
74## Important: Git Staging for Flake Evaluation
75
76**CRITICAL**: New nix files must be staged (git add) before they are available in flake evaluation. When creating new packages, modules, or any nix files, always run `git add <files>` before testing with `nix build`, `nix run`, etc.
77
78## Git Push Policy
79
80**CRITICAL**: NEVER `git push` to any remote. Local commits are fine when asked.
81A push happens only when the user runs it themselves or explicitly says
82"push" for that specific change in the current conversation. This includes
83all remotes (origin, HTTPS via gh credentials, pair) and all branches.
84
85## Machine Facts and Secrets via vars
86
87- SSH public keys
88- Network identities (retiolum, mycelium, zerotier)
89- Syncthing IDs
90- DKIM keys (for mail servers)
91
92Secrets are managed via password-store and uploaded to `/run/secrets` on deployment.
93
94## Adding New Machines
95
961. Create directory `machines/<name>/`
972. Add `config.nix`, `physical.nix`, and optionally `disk.nix`
983. Generate facts using clan-cli
994. Add to inventory in `flake.nix`
1005. Deploy using `s deploy --flake . <name>` (agents add `--yes`)
101
102## Pre-Commit
103
104**CRITICAL**: Always run `nix fmt` before committing to ensure all files pass the treefmt formatting check in CI.
105
106## Commit Message Guidelines
107
108- Use simple, descriptive commit messages without attribution footers
109- Use flake attribute paths as prefixes (e.g., `tools.mutt:` not just `mutt:`)
110- For flake.lock updates, use: "flake.lock: update"
111- Follow existing patterns seen in git log