release / govulncheck (push) Successful in 14s
release / web (push) Failing after 16s
release / go (push) Successful in 1m13s
release / integration (push) Successful in 4m54s
release / android (push) Successful in 5m5s
release / Build signed APK (releases and dev) (push) Successful in 5m18s
release / Attach APK to the Release (tag releases only) (push) Skipped
release / Build + push container image (push) Skipped
release / Verify release artifacts (tag releases only) (push) Skipped
- Library: the folders, Run scan and a row per scan job, cover art, fingerprints and loudness (off the Overview and Duplicates) - Acquisition: indexers and clients, searching, re-acquisition (off Missing files), Lidarr - Metadata sources: AcoustID, and one provider block for cover art and tags in place of the pasted pair - Email & network: outgoing email, the notification schedule, public address, proxies - Lidarr, outgoing email and the provider block are rebuilt as SettingsGroup rows; failures read as sentences, not codes - Duplicates and Missing files say what their setting is and link to where it is set Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.1 KiB
1.1 KiB
README screenshots
Drop the files below into this directory with these exact names — the
root README.md already references them, so no Markdown editing is needed.
Export as PNG. Capture while logged in as admin and after the first
library scan so nothing looks empty; keep the same browser width and theme
across all shots for a consistent look.
| Filename | Route | What to capture |
|---|---|---|
home.png |
/ |
The home page with a populated library (system playlists / recently added) |
register.png |
/register |
The account-creation form on a fresh instance |
library-scan.png |
/admin |
The library scan running in stages (grab it mid-scan so stage tallies show) |
integrations.png |
/admin/acquisition |
Indexers, download clients, searching and Lidarr |
android-download.png |
/settings |
The "Install the Android app" download card |
invite-users.png |
/admin/users |
The invite-token generation / users list |
Tip: to control display width in the README, you can swap the Markdown
 for an HTML tag, e.g. <img src="docs/screenshots/home.png" width="800" alt="...">.