Written 9 Sep 2026. This is a how-to, not a product card.

A pipeline can wait

The leftover box is the job. GitHub Actions, Terraform, and a deploy Friday can wait.

CI is robots testing every commit. Useful later, when you have code you ship more than once. The weekend path is install, SSH, Pi-hole, a folder. Tick Lab plan after those work. A green check on GitHub is not a tick.

What this is not

This is not “never learn pipelines.” It is “don't start the leftover box with a YAML file that deploys nothing.” A compose stack is already later: Docker is not the first weekend. A cluster is later still: Kubernetes is not the first lab. A rented VM is the cloud can wait.

When it can wait

If the job is ads or a house folder, you type commands on that computer. A later habit is weekly updates: keep the computer updated. That is still you, or a timer on the box — not a runner in a foreign datacenter.

What next

Weekend path: your first weekend. Tick rule: when the quiz is not the job. First service: house-wide ad block.

Optional: leftover box vs a later pipeline as a sandbox in ByteRush — same Labthrift passkey as Plan. Skip if you just want to keep reading.

Skip

• Skip GitHub Actions, GitLab CI, and Jenkins this weekend.
• Skip Terraform so the leftover box can be “as code.”
• Skip a Friday deploy of Pi-hole from a runner.