subwave-deploy

To deploy an internet radio stack with Docker Compose and verify audio, you need a workflow that rebuilds changed services and probes the stream endpoint for actual audio levels. This detects silent failures where APIs report healthy but no sound is broadcasting.

A Liquidsoap Icecast stream can show healthy but play no sound when Docker services are restarted without rebuilding changed code. Audio-level verification using an ffmpeg mean_volume probe on the stream detects this silent failure that standard health checks miss.

To update Docker Compose services without full rebuilds, map changed file paths to specific services and recreate only those containers. This minimizes churn during routine updates by targeting rebuilds to affected components rather than restarting everything.

Yes, ffmpeg and jq are required dependencies for radio deployment and health checks. ffmpeg probes stream audio levels to detect silent broadcasts, while jq parses JSON API responses from health and now-playing endpoints during validation.

The best way to bootstrap a fresh internet radio install is using an idempotent Bash setup script that seeds configuration, pulls code, and starts Docker services. This ensures consistent first-boot deployments across fresh installs and routine updates.

An ffmpeg audio probe measures the mean_volume of a live radio stream URL to verify audio is actually playing. This catches the Liquidsoap wedge where the stream connects and APIs report healthy but no audio is being broadcast to listeners.