bvandeusen
7c0f9750d8
Triggers on push to dev/main, tag pushes, PR to main, and manual dispatch — all path-filtered to flutter_client/** and the three shared web inputs the sync_shared.sh script reads. Steps: - Sync tokens/error-copy/svg from web/ via tool/sync_shared.sh - Re-run dart run tool/gen_tokens.dart and fail if lib/theme/tokens.dart drifts from shared/fabledsword.tokens.json (catches forgotten regen on the JSON edit path) - flutter pub get / analyze --fatal-infos / test - Debug APK on every push (uploaded as a workflow artifact) - Release APK on tag, attached to the corresponding Forgejo release via RELEASE_TOKEN (release.yml creates the release entry; this workflow just attaches the APK as minstrel-<tag>.apk) Uses subosito/flutter-action@v2 on ubuntu-latest for portability — no dependence on a Flutter-pre-installed runner.
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.