c4c1c2b509
Bumps the version-updates group with 7 updates in the / directory: | Package | From | To | | --- | --- | --- | | [actions/setup-node](https://github.com/actions/setup-node) | `6.3.0` | `6.4.0` | | [peaceiris/actions-gh-pages](https://github.com/peaceiris/actions-gh-pages) | `4.0.0` | `4.1.0` | | [docker/login-action](https://github.com/docker/login-action) | `3.6.0` | `4.1.0` | | [docker/setup-buildx-action](https://github.com/docker/setup-buildx-action) | `3.11.1` | `4.0.0` | | [docker/build-push-action](https://github.com/docker/build-push-action) | `6.18.0` | `7.1.0` | | [actions/upload-artifact](https://github.com/actions/upload-artifact) | `7.0.0` | `7.0.1` | | [marocchino/sticky-pull-request-comment](https://github.com/marocchino/sticky-pull-request-comment) | `3.0.3` | `3.0.4` | Updates `actions/setup-node` from 6.3.0 to 6.4.0 - [Release notes](https://github.com/actions/setup-node/releases) - [Commits]( |
||
|---|---|---|
| .devcontainer | ||
| .github | ||
| .storybook | ||
| .vscode | ||
| assets | ||
| config | ||
| deploy | ||
| docker/root/etc/s6-overlay/s6-rc.d | ||
| docsite | ||
| flatpak | ||
| patches | ||
| public | ||
| src | ||
| .dockerignore | ||
| .gitignore | ||
| .lnav.config.json | ||
| .mocharc.json | ||
| .nvmrc | ||
| cliff.toml | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| docker-compose.dev.yml | ||
| docker-compose.yml | ||
| Dockerfile | ||
| drizzle.config.ts | ||
| eslint.config.js | ||
| index.html | ||
| LICENSE | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| tsconfig.json | ||
| vite.config.ts | ||
multi-scrobbler
A dockerized app that monitors your music listening activity from everywhere and scrobbles it anywhere.
- Supports scrobbling from many Sources
- Azuracast
- Deezer
- Google Cast (Chromecast)
- Icecast
- Jellyfin
- JRiver
- Kodi
- Koito
- Last.fm
- Last.fm (Endpoint)
- Libre.fm
- ListenBrainz
- ListenBrainz (Endpoint)
- Maloja
- Mopidy
- MPD (Music Player Daemon)
- MPRIS (Linux Desktop)
- Musikcube
- Music Assistant
- Plex
- Rocksky
- Sonos
- Spotify
- Subsonic-compatible APIs (like Airsonic and Navidrome)
- teal.fm
- WebScrobbler
- VLC
- Yamaha MusicCast
- Youtube Music
- Supports scrobbling to many Clients
- Monitor status of Sources and Clients using webhooks (Gotify, Ntfy, Apprise), healthcheck endpoints, or prometheus metrics.
- Supports Now Playing for scrobble Clients
- Supports configuring for single or multiple users (scrobbling for your friends and family!)
- Web server interface for stats, basic control, and detailed logs
- Graceful network and client failure handling (queued scrobbles that auto-retry)
- Smart handling of credentials (persistent, authorization through app)
- Easy configuration through ENVs or JSON
- Modify data before scrobbling with regular expression or search patterns
- Install using Docker images for x86/ARM or locally with NodeJS
Why should I use this over a browser extension and/or mobile app scrobbler?
- Platform independent -- Because multi-scrobbler communicates directly with service APIs it will scrobble everything you play regardless of where you play it. No more need for apps on every platform you use!
- Open-source -- Get peace of mind knowing exactly how your personal data is being handled.
- Track your activity regardless of where you listen -- Scrobble from many Sources to one Client with ease and without duplicating tracks.
- Manage scrobbling for others -- Scrobble for your friends and family without any setup on their part. Easily silo sources to specific clients to keep plays separate.
But I already scrobble my music to Last.fm/ListenBrainz, is multi-scrobbler for me?
Yes! You can use Last.fm as a Source or Listenbrainz as a Source to forward scrobbles from your profile to any other Client! That way you can keep your current scrobble setup as-is but still get the benefit of capturing your data to a self-hosted location.
How Does multi-scrobbler (MS) Work?
You set up configurations for one or more Sources and one or more Clients. MS monitors all of your configured Sources. When new tracks are played by a Source MS grabs that information and then sends it (scrobbles it) to all Clients that Source is configured to forward to.
Source
A Source is a data source that contains information about music you are playing or have listened to, such as: a desktop player, web music player, or cloud music service. Examples are Spotify, Jellyfin, Plex, Youtube Music, Navidrome, etc...
Source configurations consist of:
- A friendly name.
- Any data needed to communicate or authenticate with the Source.
- An optional list of Client names that the Source should scrobble to. If omitted the Source also scrobbles to all configured Clients.
Client
A Client is an application that stores the historical information about what music you have played (scrobbles). Examples are Koito, Last.fm, Listenbrainz...
Client configurations consist of:
- A friendly name.
- Any data needed to communicate or authenticate with the Client.
Quick Start
Installation
See the Installation documentation
Configuration
See the Configuration documentation
Usage
A status page with statistics, recent logs, and some runtime configuration options can be found at
http://localhost:9078
Output is also provided to stdout/stderr as well as file if specified in configuration.
On first startup you may need to authorize Spotify and/or Last.fm by visiting the callback URL (which can also be accessed from the status page). Visit the status page above to find the applicable link to trigger this.
Help/FAQ
Having issues with connections or configuration? Check the FAQ before creating an issue!
Development
Detailed architecture and development guides for Sources/Clients
License
MIT