bvandeusen
d8bfdc1733
The repo now contains the Flutter mobile client at flutter_client/ (M7 #356). Two cleanups so the existing build pipelines don't churn on Flutter-only changes: 1. .dockerignore — keep the Flutter project (and docs/, IDE noise, git metadata) out of the Docker build context. The runtime image was already unaffected (multi-stage drops everything but the Go binary), but the COPY . . layer cache invalidated on every Flutter edit. Build context shrinks ~2.4 MB and Flutter-only pushes no longer force Go rebuilds. 2. test.yml + release.yml — paths-ignore on flutter_client/**, docs/**, and **/*.md. Go/web tests + container build now skip when the diff doesn't touch them. Tag releases still build broadly since server + Flutter ship paired. The Flutter-side workflow lands in M7 Task 21 with its own paths filter restricting it to flutter_client/** and the shared web/ inputs (tokens.json, error-copy.json, album-fallback.svg).
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.