Workflows

These are the core workflows used day-to-day. All examples use placeholders.

yeet run <svc> ./compose.yml --net=lan

Get the LAN IP:

yeet info <svc>
yeet ip <svc>

After your first run, yeet writes a yeet.toml in the project directory. You can then re-run with just the service:

yeet run <svc>

Update later (compose services; update pulls images and recreates containers):

yeet run <svc> ./compose.yml          # redeploy config, reuse existing images
yeet run --pull <svc> ./compose.yml   # pull latest + redeploy
yeet docker pull <svc>     # prefetch images without restarting
yeet docker update <svc>   # pull + recreate containers (restart)

yeet run <svc> ./Dockerfile

GOOS=linux GOARCH=amd64 go build -o ./bin/<svc> ./cmd/<svc>
yeet run <svc> ./bin/<svc>

Pull a public image on the catch host:

yeet run <svc> nginx:latest

Push a local image instead (for custom builds):

yeet docker push <svc> <local-image>:<tag> --run

For binaries or compose files, just re-run yeet run with the new payload. For compose images, add --pull (or use yeet docker update) when you want to refresh images.

yeet run <svc> ./bin/<svc>

yeet stage <svc> ./bin/<svc>
yeet stage <svc> show
yeet stage <svc> commit

yeet edit <svc>          # compose or systemd units
yeet env edit <svc>       # env file
yeet env copy|cp <svc> ./app.env
yeet env set <svc> PORT=8080 LOG_LEVEL=debug
yeet env set <svc> LOG_LEVEL=     # unset

yeet copy ./app.env <svc>:
yeet copy ./config.yml <svc>:config/config.yml
yeet copy ./configs/ <svc>:config/

yeet cron <svc> ./job.sh "0 9 * * *" -- --job-arg foo

yeet logs -f <svc>

Here, <host> refers to the catch host (Tailscale/tsnet hostname), not the SSH machine host. See Tailscale.

Set the host per command:

CATCH_HOST=<host> yeet status

Or use @host:

yeet status@<host>
yeet run <svc>@<host> ./compose.yml

Or save it:

yeet prefs --host=<host> --save