Skip to content

v2.0.1

Choose a tag to compare

View all tags
@github-actions github-actions released this 30 Oct 19:05
· 179 commits to main since this release
v2.0.1
This tag was signed with the committer’s verified signature.
InstaZDLL
GPG key ID: 41068F83E2A5B95F
Verified
Learn about vigilant mode.
000a650
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

WaveFlow Server 2.0.1

A small release after 2.0.0: a ready-made way to put the server behind HTTPS, and one needless boot warning removed.

New

  • HTTPS with Caddy, ready to copy. packaging/caddy/ holds a compose file and a Caddyfile that run the server behind Caddy. Set the name your clients will use in a .env and run docker compose up -d. A public name gets a certificate from Let's Encrypt, or from ZeroSSL when Let's Encrypt cannot issue one. A name ending in .internal or .home.arpa, or an IP address, gets one from Caddy's own local authority. The server publishes no port of its own, and the proxy is already trusted, so sign-in protection counts each client by its own address.

    The operations guide explains how to make your devices trust the local authority, why an untrusted certificate stops offline listening in the browser, why most Android apps refuse the local authority even once you install it, how to move a server you already run onto this setup without losing its data, and what to write for nginx instead.

Fixed

  • A server that never asked for Last.fm no longer warns about it at every boot. The warning now appears only when you named a Last.fm instance yourself, with WAVEFLOW_SCROBBLE_LASTFM_URL.

Install

docker run -d --name waveflow \
  -p 4533:4533 \
  -v waveflow-data:/data \
  -v /path/to/music:/music:ro \
  ghcr.io/instazdll/waveflow-server:2.0.1

The image runs on linux/amd64 and linux/arm64, and is the same, digest for digest, on Docker Hub as instazdll/waveflow-server:2.0.1. latest now follows this release.

Upgrading from 2.0.0

Pull 2.0.1 and start it on the same data volume. The database schema has not changed, so there is nothing to migrate, and 2.0.0 still opens the same volume should you need to go back.

To move onto the Caddy setup, stop the server you run now before starting the new one, and point the new compose file at your existing volume with WAVEFLOW_DATA_VOLUME: the guide's "Moving an existing server" walks through it. Started without that line, it begins on a new, empty volume.

Full changelog: CHANGELOG.md · v2.0.0...v2.0.1

Container image

docker pull ghcr.io/instazdll/waveflow-server:2.0.1

The same image, digest for digest, is on Docker Hub:

docker pull instazdll/waveflow-server:2.0.1

Also published as latest in both, for linux/amd64 and linux/arm64 (a Raspberry Pi 4 or 5 on a 64-bit system).

Assets 2
Loading