bvandeusen
17406eebee
M5a is the foundation slice of M5 (Lidarr integration + quarantine). Decomposed into M5a/M5b/M5c during brainstorming on 2026-04-29: - M5a (this spec) — Lidarr connection + search/add + admin shell - M5b — Quarantine workflow (per-user soft-hide, admin resolution) - M5c — Radio suggested-additions (out-of-library MBIDs surfaced) Each ships as its own PR with its own brainstorm/spec/plan cycle. Key decisions captured: - Permissions: search-all, add-admin via request queue - Config: DB-only, Settings UI is the only entry point (no YAML) - Settings shape: dedicated /admin/* route group, hard route gate - Search UX: standalone /discover route, all three granularities - Lifecycle: library scan as source of truth + 5-min reconciler worker - Quality profile/root folder: default + per-add admin override - UI lands at FabledSword design system bar (forest-teal accent; Moss/Bronze/Oxblood action buttons; per project_design_system memory) Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Minstrel
Self-hosted music server with OpenSubsonic compatibility plus an extended API for server-side smart shuffle, a dual-like model (general + contextual), session-aware radio, ListenBrainz scrobble/similarity, and Lidarr integration. Go + Postgres, packaged as a Docker container.
State and intelligence belong on the server, not the client.
Specs
Authoritative v1 scope lives under docs/:
- Server spec — current implementation focus.
- Client spec — Flutter companion app; work starts once the server reaches its Subsonic-compatible baseline.
Development workflow
- Day-to-day work happens on the
devbranch (or feature branches merged intodev). mainis protected — changes land only via pull request fromdev.- Production builds are cut by tagging a release (
v*) offmain.
CI / container image
Forgejo Actions handles:
- Tests on push to
devand on PRs intomain. - Container image build + push to the Forgejo registry on merge to
main(:main) and onv*tags (:<version>).
Task and milestone tracking: Fable (Minstrel project, id 12).
Development
Minstrel has two concurrent dev processes:
- Backend:
docker compose up— starts Postgres and Minstrel on:4533. - Frontend:
cd web && npm install && npm run dev— Vite dev server on:5173with HMR.
The Vite dev server proxies /api/* and /rest/* to the backend on :4533,
so session cookies work correctly when the SPA is loaded from the Vite origin.
Production build
docker build -t minstrel . runs the SvelteKit build inside a node stage,
copies the output into the golang stage, and //go:embeds it into the
final binary. The resulting container serves the SPA from / alongside the
API surfaces. No separate static-file server is required.