Yeet Docs
A focused user manual for the yeet + catch homelab workflow.
Note
Yeet is personal infrastructure tooling tuned for a specific homelab. Use it as a reference or starting point, not a general-purpose platform.
Tip
If you use an AI coding tool that supports
npx skills, see Installation for the optionalyeetagent skill install.
Architecture
How yeet and catch work together over Tailscale RPC.
Networking
Network modes, service IPs, and tailscale options.
Tailscale
RPC, service netns, and Tailnet routing details.
Service Types
Payload detection and install behavior by type.
Configuration & Prefs
Client preferences, yeet.toml, and environment variables.
Yeet CLI
Full command reference for yeet.
Catch CLI
Catch flags and RPC surface overview.
Data Layout
On-host storage structure and service directories.
Troubleshooting
Common failure modes and fixes.
Development
Local dev setup and build/test commands.
FAQ
Short answers to common questions.
- Catch runs on each host, and yeet runs from the workstation.
- Services are deployed over Tailscale RPC with explicit network modes (see Tailscale).
- Host targeting and defaults are driven by
CATCH_HOSTandyeet.toml.
<svc>means a service name.<host>means a host name oruser@host.<file>means a local file path.- Code blocks are intended to be copy-pasteable.