Service Types

Yeet detects payload type and installs the service accordingly.

• ELF or Mach-O binary.
• Installed as a systemd service on the host.
• Use yeet run <svc> ./bin/<svc>.

• Shebang file (e.g., #!/usr/bin/env bash).
• Treated like a binary; installed as a systemd service.

• Any YAML with a top-level services: key.
• Installed as a docker compose service.
• Use --pull on yeet run when you want to refresh images; otherwise run reuses existing images.
• Configure port mappings in the compose file.

yeet run <svc> ./compose.yml

• If the payload looks like an OCI image ref (e.g. nginx:latest, ghcr.io/org/app:1.2.3), yeet generates a compose file and catch pulls the image on the host.
• For local images, use yeet docker push <svc> <image>:<tag> --run.
• For Dockerfiles, use yeet run <svc> ./Dockerfile (builds for the host arch and pushes).
• Use -p/--publish with yeet run to expose ports (e.g. -p 8000:8000).

• .ts files are run via a Deno container.
• Installed as a docker compose service (via Deno).
• Use -p/--publish with yeet run to expose ports (e.g. -p 8000:8000).

• .py files are run via a uv container image.
• Installed as a docker compose service (via uv).
• Use -p/--publish with yeet run to expose ports (e.g. -p 8000:8000).

• Zstd-compressed binaries are detected and unpacked.

• yeet cron installs a cron-style job as a timer on the host.

• File type is detected by extension or content.
• Architecture must match the target host; mismatches fail early.