MANUAL · 10

The operator console.

SUB/WAVE ships a command-line console for running the station. One command opens a menu that boots the stack, checks its health, tails logs, and opens the web player or admin, with no Docker flags to remember.

PRESS START

One command opens the console.

Run subwave with no arguments. The console is a menu: arrow keys to move, Enter to choose, Esc to step back, Ctrl-C to quit.

SHsubwave

First time through? If there’s no .env yet, the console drops you straight into the install wizard, the same one the setup guide walks through.

Working from a cloned repo instead of the standalone CLI? Run npm start; it opens the same console.

WHAT THE MENU OFFERS

Everything you need to run the station.

The menu adapts to what’s running. When the stack is down you only see start; when it’s up, the running-stack actions take its place.

status— a quick snapshot: which stack is up, how many containers are running, and what’s on the air right now.
doctor— a full diagnostic sweep: the Docker daemon, every container, the controller’s HTTP health, Navidrome reachability, and recent errors in the logs.
start / stop — bring the stack up or down. Starting from cold asks whether you want the dev or production layout.
restart — rebuild and recreate a single service. The console knows the controller and Liquidsoap need a rebuild (not a plain restart) for source changes to take.
logs — tail one service, or all of them, without the long docker compose -f … incantation.
listen — open the web player in your browser.
admin — open the admin console in your browser.
setup — re-run the install wizard.

HEALTH AT A GLANCE

Status for a glance, doctor for a deploy.

status is the two-second “is it on the air?” check. doctoris the deeper sweep. Run it after a deploy, or when something looks off. It’s the console’s equivalent of scripts/health-check.sh, and it ends with an ok / warn / fail tally plus a hint at the first thing that’s unhappy.

CONSOLES

Jump straight to the web player or the admin.

listen and admin open the web player and the admin console in your default browser, pointed at the same stack, with no host or port to remember. For tuning in from outside the browser, the Listen With page covers VLC, cliamp, and the native apps.

SCRIPTING IT

Every action runs without the menu too.

The menu is for hands-on operating. To skip it (for a deploy script, a cron job, or just speed), name the action straight after subwave:

SHsubwave status
subwave doctor
subwave logs controller
subwave restart controller

Same actions, same output, just without the interactive menu wrapped around them. From a cloned repo, the same actions run after npm start -- (e.g. npm start -- status).

One command opens the console.

Run subwave with no arguments. The console is a menu: arrow keys to move, Enter to choose, Esc to step back, Ctrl-C to quit.

subwave

First time through? If there’s no .env yet, the console drops you straight into the install wizard, the same one the setup guide walks through.

Working from a cloned repo instead of the standalone CLI? Run npm start; it opens the same console.

Everything you need to run the station.

The menu adapts to what’s running. When the stack is down you only see start; when it’s up, the running-stack actions take its place.

status— a quick snapshot: which stack is up, how many containers are running, and what’s on the air right now.

doctor— a full diagnostic sweep: the Docker daemon, every container, the controller’s HTTP health, Navidrome reachability, and recent errors in the logs.

start / stop — bring the stack up or down. Starting from cold asks whether you want the dev or production layout.

restart — rebuild and recreate a single service. The console knows the controller and Liquidsoap need a rebuild (not a plain restart) for source changes to take.

logs — tail one service, or all of them, without the long docker compose -f … incantation.

listen — open the web player in your browser.

admin — open the admin console in your browser.

setup — re-run the install wizard.

Every action runs without the menu too.

The menu is for hands-on operating. To skip it (for a deploy script, a cron job, or just speed), name the action straight after subwave:

subwave status subwave doctor subwave logs controller subwave restart controller

Same actions, same output, just without the interactive menu wrapped around them. From a cloned repo, the same actions run after npm start -- (e.g. npm start -- status).