Settings
Qobuz authentication
Qobuz has no public login, so the app reuses the token your own browser
already holds — you copy it once, and it's stored only on your server,
never sent anywhere but Qobuz. To find it (about 30 seconds): sign in at
play.qobuz.com, open dev tools (F12) → Application → Local Storage →
play.qobuz.com, and copy the localuser entry's
token — the id next to it is your user ID.
Mode
The web app and the command-line tool can't run at the same time — they share one download lock. Hand control to the terminal here, run your CLI commands (docker exec -it qobuz-librarian qobuz-librarian), then resume. Downloads in the web UI are paused while the terminal has control.
Behaviour
These take effect on the next job — no restart needed. They override the
defaults from compose.yaml.
Container paths
Where the container reads and writes inside its own filesystem.
The defaults work for a normal Docker install — only worth touching
if you've changed the bind mounts in compose.yaml. A
restart is required after editing.
- MUSIC_ROOT
- /music
- STAGING_DIR
- /staging
- BEETS_DB_PATH
- /config/beets/musiclibrary.db
- STREAMRIP_CONFIG
- /config/streamrip/config.toml
Diagnostics
Read-only checks from the container's point of view. Run these before your first scan to catch an unmounted or unwritable volume.