goose knows about nix
This commit is contained in:
1 parent
25fcf85855
commit
25f648d606
8 files changed
+35
-11
No files matched your search
+2
-2
@@ -2,9 +2,9 @@
|
||||
|
||||
## Requirements
|
||||
|
||||
- Linux with systemd (`systemd-nspawn`, `systemd-machined`, `systemd-networkd`), running as root.
|
||||
- Linux with systemd (`systemd-nspawn`, `systemd-machined`, `systemd-networkd`), running as root. Containers run with user namespacing and ID-mapped mounts, so you need systemd 250 or newer and a kernel that supports ID-mapped mounts for the filesystems holding `/nix/store`, `state_dir` and the drives (btrfs, ext4 and xfs on any recent kernel).
|
||||
- One or more **btrfs** folders for home folders. Quotas are switched on automatically.
|
||||
- Nix with flakes, to build the bot and the container system. NixOS is easiest, but not required.
|
||||
- Nix with flakes, to build the bot and the container system. NixOS is easiest, but not required. It has to be a multi-user install with `nix-daemon` running: containers build through `/nix/var/nix/daemon-socket`, and won't start without it. The daemon sees containers as untrusted users (they run as unprivileged host uids), so `trusted-users` needs no changes, but `allowed-users` must still allow everyone (the default `*`). Their builds go into the host's store, so run `nix-collect-garbage` or `nix.gc` now and then.
|
||||
- An API key for the model goose should use (e.g. Anthropic).
|
||||
|
||||
## 1. Slack app
|
||||
|
||||
Reference in new issue
Block a user