The Problem

Why the manual approach falls over

One Mac is delightful. Two is convenient. Five is a project. Nine is operations. Each new machine multiplies the work — every update, every config change, every health check happens N times unless you've automated it. Logging into machines one by one doesn't scale past three.

The fleet approach in one sentence

With the right SSH config, host lists, and a few small shell helpers, you can update every Mac in parallel, deploy config in one command, and run a 30-second daily health check across the whole fleet. Same machines, dramatically less ceremony.

You don't need enterprise tools yet

Puppet, Chef, Salt, full Ansible Tower — those exist for fleets in the hundreds with multi-team operations. For 5–20 personal/small-business Macs, SSH loops + a Brewfile + maybe ad-hoc Ansible is plenty. We'll cover Ansible later in this track for the cases where it pays for itself.

Code

The serial pain·bash

# Updating 8 Macs the manual way
ssh office  'brew update && brew upgrade'  # wait...
ssh server  'brew update && brew upgrade'  # wait...
ssh music   'brew update && brew upgrade'  # wait...
ssh macbook 'brew update && brew upgrade'  # wait...
# ... 4 more, half an hour later

The parallel cure (preview)·bash

# A simple parallel pattern (we'll build this up over the track)
for host in office server music macbook pro2024 pro2023 air mini; do
    ssh -o ConnectTimeout=5 "$host" 'brew update && brew upgrade' &
done
wait
echo 'all done'

Exercise

List every machine you SSH into in a typical month. Estimate how many minutes of toil per month each one costs you (updates, config drift, daily health). Multiply by 12 for a year. That number is the budget for fleet automation. By the end of this track, you'll spend most of it once and reclaim the rest.