Plan the server
In this lesson I plan a Mac mini as an always-on home server and I start the git repository that will hold every step of its setup. By the end of the course you can rebuild the same server from that repository on a clean Mac. Before you start you need a Mac with Apple silicon, a recent macOS, an administrator account and the terminal app. You also need Git. If Git version offers to install the command line developer tools, accept and run it again. This first command checks all three, the macOS version, the processor architecture where ARM64 means Apple silicon and the Git version. First, what the machine has. The system profiler knows the model, the chip, the cores and the memory. I keep only both lines because the full report also shows the serial number. 12 cores, 8 for performance and 4 for efficiency and 48 gigabytes of memory. The processor and the GPU, the graphics processor share that memory, then the free disk space. With the hardware known a server needs three decisions. The first one, how do I reach it this mac runs headless with no monitor and no keyboard and i manage it from a laptop over ssh the secure shell turning on ssh needs an administrator password so it has its own lesson here i only ask whether something listens on port 22 the ssh port something does a remote login is already on for this Mac. The second decision is FileVault, the disk encryption of macOS. This command reads its state and it needs no password. FileVault is off here and that is a trade-off. With FileVault on, a stolen disk is unreadable but after every restart someone has to type the password before the server comes back. With it off, the Mac restarts on its own after a power I keep it off on this server so that it comes back by itself. If yours could be stolen, turn FileVault on and plan for that password. The third decision is what runs where. Linux containers need a Linux virtual machine, a VM, and on this server that is one VM managed by Kolima. A VM cannot use the Apple GPU, so anything that needs the GPUs, such as language models that run on the Mac itself, runs natively on macOS. Now I write these decisions down in a new Git repository called Mac Mini Home Lab. Every file that sets up the server will live in it. The plan has three parts. The machine, as I just read it, the three decisions. In a small diagram, the laptop reaches the Mac over SSH, Homebrew installs the tools, GPU work stays native, and containers run in the Colima VM. The last two lines matter for the whole course. The repository holds what the server should be, logs and other machine data go to a separate folder, Homelab data, which is never in Git. The plan is the first commit. You now know what your Mac has, how you will reach it, whether file vault stays on, what runs natively and what runs in a VM, and all of it is written in a repository that the rest of the setup builds on.