mirror of
https://github.com/FoxxMD/multi-scrobbler.git
synced 2026-10-21 13:53:29 +00:00
6fa5ea47a0
Add optional clientId/clientSecret config for a Mixcloud application. When both are defined the source runs the OAuth authorization flow (redirecting through /api/mixcloud/callback), persists the received access token next to the config like the spotify source, and reads listens from /me/listens/ -- which includes the private and pro listening history the public endpoint does not expose. The username is discovered from the authorized user's profile. With only a username the source behaves exactly as before, so existing configs keep working unchanged. |
||
|---|---|---|
| .. | ||
| applemusic.json.example | ||
| azuracast.json.example | ||
| chromecast.json.example | ||
| config.json.example | ||
| deezer-deprecated.json.example | ||
| deezer.json.example | ||
| discord-local.json.example | ||
| discord.json.example | ||
| endpointlfm.json.example | ||
| endpointlz.json.example | ||
| icecast.json.example | ||
| jellyfin.json.example | ||
| jriver.json.example | ||
| kodi.json.example | ||
| koito.json.example | ||
| lastfm.json.example | ||
| librefm.json.example | ||
| listenbrainz.json.example | ||
| maloja.json.example | ||
| mixcloud.json.example | ||
| mopidy.json.example | ||
| mpd.json.example | ||
| mpris.json.example | ||
| musiccast.json.example | ||
| musikcube.json.example | ||
| plex.json.example | ||
| README.md | ||
| rocksky.json.example | ||
| sonos.json.example | ||
| spotify.json.example | ||
| subsonic.json.example | ||
| tealfm.json.example | ||
| tuneshine.json.example | ||
| vlc.json.example | ||
| webscrobbler.json.example | ||
| ymbridge.json.example | ||
| ytmusic.json.example | ||
These are example configurations for all Source/Client types and AIO config.
These can be used as-is by renaming them to .json and filling or replacing sample data.
For docker installations these examples are copied to your configuration directory on first-time use.
These are NOT exhaustive examples. You should consult the configuration documentation and the schema explorer links for each source/config type to see a complete list of options and descriptions for all properties.
Documentation at