One small, static binary per device — pure Go, no runtime, no dependencies. Pick the path that fits your setup; every one ends with a node on your network in a few minutes.
Just run it
the basics
Grab the build for your hardware, unpack it, and run it. No flags required — it picks sensible defaults, finds your audio device, and joins the cluster on its own. That’s the whole setup.
The quickest way onto a Linux box: a guided one-liner. It detects your OS and CPU, downloads the matching build, then walks you through the optional extras — Spotify Connect and a boot-time service — and sets them up. Installs into /usr/local/lib/ondaire; re-run any time to update.
Run a master on a NAS or server: mount your music library read-only and serve it to your players, with Spotify Connect built in. The container sources and controls audio; output happens on your players, not in the container.
--network host is required. Players discover the master over mDNS and go-librespot advertises Spotify Connect over zeroconf — multicast doesn’t cross Docker’s bridge network.
Start at boot (systemd)
always on
Want ondaire to come up with the machine and restart on failure? The guided installer offers to write and enable a systemd service for you — no hand-editing unit files. Choose “yes” when it asks, or set it up later following the user guide.
Turn a PSRAM-equipped ESP32 + an I2S DAC into a real ondaire player: it shows up in the cluster, joins any group, and plays in lock-step like every other room — flashed straight from your browser, no toolchain. Tested on the ESP32-S3 Super Mini and Waveshare ESP32-S3-Zero with a PCM5102A DAC.