Find a file
FoxxMD 6780d72296 Improve testing, linting, and node usage in devcontainer
* Swtch to devcontainer for node 18.x and remove terminal/launch settings for version (removes nvm dependency in container)
* Update eslint config to use proper config for include/ignore files
* Add spec for mocha and mocha test runner extension + settings
2024-10-08 19:33:47 +00:00
.devcontainer Improve testing, linting, and node usage in devcontainer 2024-10-08 19:33:47 +00:00
.github Add multi-runner WIP tests to ACT 2024-09-27 16:30:02 -04:00
.vscode Improve testing, linting, and node usage in devcontainer 2024-10-08 19:33:47 +00:00
assets docs: Update screenshot 2024-07-09 09:51:33 -04:00
config fix(jellyfin): Fix naming in documentation for allow/disallow options 2024-09-30 11:07:43 -04:00
docker/root/etc/s6-overlay/s6-rc.d Working dockerfile 2024-01-18 16:59:45 -05:00
docsite docs: Update/fix docker-compose usage 2024-10-03 09:11:56 -04:00
flatpak chore: Bump version for release 2024-09-27 09:02:04 -04:00
patches chore: Update schema 2024-08-22 16:44:15 -04:00
public Update index.html 2024-01-19 11:05:34 -05:00
src Improve testing, linting, and node usage in devcontainer 2024-10-08 19:33:47 +00:00
.dockerignore Add multi-runner WIP tests to ACT 2024-09-27 16:30:02 -04:00
.gitignore Add multi-runner WIP tests to ACT 2024-09-27 16:30:02 -04:00
.mocharc.json Improve testing, linting, and node usage in devcontainer 2024-10-08 19:33:47 +00:00
.nvmrc chore(!): Upgrade Node to LTS for --import support 2024-02-15 12:40:02 -05:00
.nycrc.json refactor: Restructure server directory 2023-08-24 11:12:27 -04:00
alpine.Dockerfile docs(fix): Add missing docsite build steps to alpine docker variant 2024-07-15 13:50:37 -04:00
cliff.toml chore: Add git-cliff template 2023-06-07 10:01:30 -04:00
CONTRIBUTING.md chore: Refactor git/dev workflow to use master as unstable branch 2024-08-30 09:53:52 -04:00
docker-compose.yml docs: Update/fix docker-compose usage 2024-10-03 09:11:56 -04:00
Dockerfile docs: Implement self-hosted docs 2024-07-15 13:26:57 -04:00
eslint.config.js Improve testing, linting, and node usage in devcontainer 2024-10-08 19:33:47 +00:00
index.html Update index.html 2024-01-19 11:05:34 -05:00
LICENSE Create LICENSE 2020-12-06 21:51:20 -05:00
package-lock.json chore: Bump version for release 2024-09-27 09:02:04 -04:00
package.json Improve testing, linting, and node usage in devcontainer 2024-10-08 19:33:47 +00:00
postcss.config.js It works! 2024-01-18 14:18:08 -05:00
README.md docs: Fix link typo for flatpak 2024-10-03 09:18:26 -04:00
tailwind.config.js It works! 2024-01-18 14:18:08 -05:00
tsconfig.json somewhat working esm conversion 2024-01-18 13:15:06 -05:00
typedoc.json feat: Implement somewhat-working docusaurus site 2023-07-13 15:08:00 -04:00
vite.config.ts fix: Don't use es module in vite config because of gross esm/cjs reasons 2024-09-13 17:07:32 -04:00

multi-scrobbler

Latest Release License: MIT Docker Pulls Docs

multi-scrobbler logo

A javascript app to scrobble music you listened to, to Maloja, Last.fm, and ListenBrainz

Quick Start Guide

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 it grabs that information and then sends it (scrobbles it) to all Clients that Source is configured to scrobble to.

Source

A Source is a data source that contains information about tracks you are playing like a music player or platform. Examples are Spotify, Jellyfin, Plex, Youtube Music, Airsonic, 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 songs you have played (scrobbles). Examples are Maloja, Last.fm, Listenbrainz...

Client configurations consist of:

  • A friendly name.
  • Any data needed to communicate or authenticate with the Client.

Quick Start

See the Quick Start Guide

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