deploy — OS-level configs for llamaclaw¶

Launchd plists, systemd units, kernel tuning, and udev rules for running llamaclaw in production¶

Layout · Quick start · Security · License

Config files, service units, kernel-tuning rules, and launchers that run the llamaclaw ecosystem on macOS and Raspberry Pi 5. Pure ops — nothing statistical or AI-related.

Part of the llamaclaw ecosystem.

Layout¶

Path	Host	What
`yodavision/mac/`	macOS	launchd plist (ESML coord-fetch background task)
`yodavision/zeus/`	Pi 5 (zeus.local)	systemd units, kernel tuning (`99-esml-luci-sysctl.conf`), NVMe BFQ (`00-nvme-bfq.rules`), shell env, universe dir
`deploy/raspberry-pi/`	Pi	production service units: `esml-ollama.service`, `perseus-relay.service`

Filenames are kept historical (yodavision/mac/...) so git history matches the monorepo — future cleanup can rename into a flatter tree.

Quick start¶

macOS¶

cp yodavision/mac/com.esml.coord-fetch.plist ~/Library/LaunchAgents/
launchctl load ~/Library/LaunchAgents/com.esml.coord-fetch.plist

Raspberry Pi 5 (zeus.local)¶

# Kernel tuning
sudo cp yodavision/zeus/00-nvme-bfq.rules /etc/udev/rules.d/
sudo cp yodavision/zeus/99-esml-luci-sysctl.conf /etc/sysctl.d/
sudo udevadm control --reload && sudo sysctl --system

# Services
sudo cp deploy/raspberry-pi/*.service /etc/systemd/system/
sudo systemctl daemon-reload
sudo systemctl enable --now esml-ollama.service perseus-relay.service

See yodavision/zeus/APPLY_NOTES.md for the full step-by-step.

Security notes¶

No secrets in this repo. Service units expect .env files next to them — not tracked; documented in APPLY_NOTES.md.
All units run as dedicated users — luci or perseus, never root.
NVMe scheduler flip (00-nvme-bfq.rules) is reversible.

License¶

GPL-3.0-or-later. See LICENSE.