Skip to content

Drop invalid --host/--port flags from beet web invocation

jedmund requested to merge jedmund/beets-web-host-flag-fix into main

After PR #35 fixed the dash-shebang crash, the beets container advanced to a new failure: the uvicorn wrapper starts healthy, but beet web exits immediately with:

beet web: error: no such option: --host

beets 1.6.1's beet web plugin reads host/port from config.yaml under the web: block (already set to 0.0.0.0:8337), not from CLI flags. Dropping the flags fixes it.

Test plan

  • Redeploy (make deploy-album-sort)
  • docker logs album_sort_beets shows both uvicorn AND beet web listening on 0.0.0.0:8337, no restart loop
  • /settings page: Wrapper + Web plugin pills both reachable

Merge request reports