Yeet Docs
Docs for installing yeet, deploying services, and operating catch hosts.
Yeet runs from your workstation. Catch runs on each Linux host. Together they install services, move files, start units, tail logs, and remove services when you ask.
Start with the smallest working path. Then open the page that matches the host, payload, network, or operation in front of you.
Set up Tailscale
Create the tag policy and OAuth credential catch needs before init.
Choose what to run
Pick containers, binaries, cron jobs, or VMs by what the workload needs.
Organize service files
Keep third-party apps, env files, custom payloads, and yeet.toml in one workspace.
Operate a service
Update, restart, tail logs, edit config, stage changes, and copy files from the CLI.
Fix a problem
Start with common connection, Docker, networking, VM, and cleanup failures.
Use these when the service or host has more specific requirements.
Host targeting
Understand machine hosts, catch hosts, CATCH_HOST, and svc@host syntax.
Choose networking
Pick reachability, DNS, and outbound internet paths as one decision.
Run VMs
Create Ubuntu, NixOS, or imported microVMs and manage images, resources, files, and recovery.
Use recovery points
Use ZFS service roots, snapshots, clone-first recovery, and VM restore.
Use reference pages after you know the workflow you want. References are maps, not tutorials.