--- sidebar_position: 1 title: Overview description: Installation --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import CodeBlock from '@theme/CodeBlock'; import ComposeStack from '!!raw-loader!../../../docker-compose.yml'; :::tip For the difference between **ENV** and **File** examples in this document see [Configuration Types](../configuration/configuration.mdx#configuration-types). ::: ## Docker Cross-platform images are built for x86 (Intel/AMD) and ARM64 (IE Raspberry Pi) :::info[Available Images] [Repository Page](https://hub.docker.com/r/foxxmd/multi-scrobbler) ``` docker.io/foxxmd/multi-scrobbler:latest ``` [Repository Page](https://github.com/FoxxMD/multi-scrobbler/pkgs/container/multi-scrobbler) ``` ghcr.io/foxxmd/multi-scrobbler:latest ``` ::: ### Recommended Settings You **should** bind a host directory into the container for storing configurations, credentials, database, and other files. Otherwise, these will be lost when the container is updated. ```yaml title="docker-compose.yml" services: multi-scrobbler: # ... // highlight-start volumes: - "./config:/config" // highlight-end ``` Optionally, use a separate directory for data (database, cache, etc...) by mounting an additional directory and setting the `DATA_DIR` ENV to the directory that should be used inside the container: ```yaml title="docker-compose.yml" services: multi-scrobbler: # ... environment: # ... // highlight-start - DATA_DIR=/msData // highlight-end volumes: - "./config:/config" # used for config files // highlight-start - "./my/host/folder:/msData" # used for data files // highlight-end ``` If you are using a [bridge network](https://www.appsdeveloperblog.com/docker-networking-bridging-host-and-overlay/) (default docker setup) you must map a port to the container in order to access the dashboard and use MS with some sources (Webscrobbler, LFM/LZ Endpoints). The default container port is `9078`. ```yaml title="docker-compose.yml" services: multi-scrobbler: # ... // highlight-start ports: - "9078:9078" // highlight-end ``` :::important If your machine is accessible from the public internet consider installing multi-scrobbler on a different, private machine. **Read [Securing Multi-Scrobbler](/configuration/security)** ::: **Optionally**, when * using a [Source or Client](../configuration/configuration.mdx) that has a "Redirect URI" that you have not explicitly defined * and * using a bridge network or * installing MS on a different machine than the one used to view the dashboard set the [Base URL](../configuration/configuration.mdx#base-url) as the IP/domain of the host machine. (This is the IP you would use to view the dashboard in a browser) ```yaml title="docker-compose.yml" services: multi-scrobbler: # ... environment: // highlight-start - BASE_URL=http://hostMachineIP // highlight-end ``` When deploying MS to a domain where it will be served under a **subpath**, like `http://mydomain.com/multiscrobbler`, you **must** define `BASE_URL`: ```yaml title="docker-compose.yml" services: multi-scrobbler: # ... environment: // highlight-start # multi-scrobbler served under this subpath - BASE_URL=https://mydomain.com/multiscrobbler // highlight-end ``` This is **not required** when the root path is `/`, like `https://my-scrobbler.com` or `scrobbler.mydomain.com`. Multi-Scrobbler's docs are at [docs.multi-scrobbler.app](https://docs.multi-scrobbler.app/) but they are also generated and hosted on your instance. If you are using a **subpath** and need these self-hosted docs as well you will need to **build your own docker image.** This is a limitation of Docusaurus, the framework the docs are built on. This build step is *optional* and not required for MS to run with a subpath, you just won't have self-hosted docs and will need to use the official, hosted docs instead. To build MS with self-hosted docs, provide the same `BASE_URL` used above as a build arg: ```yaml title="docker-compose.yml" services: multi-scrobbler: // highlight-start ## remove/comment out official image # image: docker.io/foxxmd/multi-scrobbler:latest ## add build spec build: context: https://github.com/FoxxMD/multi-scrobbler.git args: - BASE_URL=https://mydomain.com/multiscrobbler // highlight-end # ... environment: # ... // highlight-start # multi-scrobbler served under this subpath - BASE_URL=https://mydomain.com/multiscrobbler // highlight-end ``` Set the [timezone](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones) for the container using the environmental variable `TZ`. ```yaml title="docker-compose.yml" services: multi-scrobbler: # ... environment: # Specify timezone from TZ Database name found here https://en.wikipedia.org/wiki/List_of_tz_database_time_zones // highlight-start - TZ=America/New_York // highlight-end ``` If you are running this container with **Docker** on a **Linux Host** you **should** specify `user:group` permissions of the user who owns the **configuration and data directories** on the host to avoid [docker file permission problems.](https://ikriv.com/blog/?p=4698) These can be specified using the [environmental variables **PUID** and **PGID**.](https://docs.linuxserver.io/general/understanding-puid-and-pgid) To get the UID and GID for the current user run these commands from a terminal: * `id -u` -- prints UID * `id -g` -- prints GID MS can be hardended by setting the file system as read only with [`read_only`](https://docs.docker.com/reference/compose-file/services/#read_only), with a few exceptions: ```yaml title="docker-compose.yml" services: multi-scrobbler: image: foxxmd/multi-scrobbler # ... // highlight-start read_only: true tmpfs: - /run:exec - /tmp:noexec // highlight-end ``` **Optionally**, add a [Valkey](https://valkey.io/) service to your stack for [secondary caching](/configuration#secondary-caching) to take advantage of faster performance, reduced memory usage, and cached api calls to external services. ```yaml title="docker-compose.yml" services: multi-scrobbler: image: foxxmd/multi-scrobbler # ... environment: # ... // highlight-start CACHE_VALKEY=redis://valkey:6379 // highlight-end # ... // highlight-start valkey: image: valkey/valkey volumes: - valkeydata:/data volumes: valkeydata: driver: local // highlight-end ``` ### Docker Usage Example :::tip See the [**Quick Start Guide**](/quickstart) for another guided docker-compose example ::: The example scenario: * [Jellyfin **Source**](/configuration/sources/jellyfin) * [Maloja **Client**](/configuration/sources/maloja) * Serving app on port `9078` * Docker container located on a different IP (`192.168.0.100`) so use [Base URL](/configuration#base-url) * Config/data directory on host machine in a directory next to `docker-compose.yml` * Linux uid/gid is `1000:1000` * Optional caching using valkey (after uncommenting) See [`docker-compose.yml`](#docker) sample above for more options and annotations. ```yaml title="docker-compose.yml" services: multi-scrobbler: image: foxxmd/multi-scrobbler container_name: multi-scrobbler environment: - TZ=Etc/GMT # Specify timezone from TZ Database name found here https://en.wikipedia.org/wiki/List_of_tz_database_time_zones - JELLYFIN_APIKEY=c9fae8756fbf481ebd9c5bb56bd6540c - JELLYFIN_URL=192.168.0.101:8096 - JELLYFIN_USER=MyUser - BASE_URL=http://192.168.0.100:9078 - MALOJA_URL=http://domain.tld:42010 - MALOJA_API_KEY=1234 - PUID=1000 - PGID=1000 # uncomment along with valkey service/volume below for better caching #- CACHE_VALKEY=redis://valkey:6379 volumes: - ./config:/config ports: - 9078:9078 restart: unless-stopped #valkey: # image: valkey/valkey # volumes: # - valkeydata:/data #volumes: # valkeydata: # driver: local ``` ## Local Installation After installation see [As a Service](/installation/service) to configure multi-scrobbler to run automatically in the background. ### Nodejs Clone this repository somewhere using the latest [git tag](/updating#git) and then install from the working directory. ```shell git clone --branch https://github.com/FoxxMD/multi-scrobbler.git cd multi-scrobbler nvm use # optional, to set correct Node version npm install npm run docs:install && npm run build npm run start ``` Pass ENVs directly to `node`/`npm`, or make a new `.env` (using `.env.example` as a reference), to configure MS for basic settings and [**Persistent Directories**](./?#persistent-directories) for config/data/log directories. #### Usage Examples :::note Regardless of the config type you are using, some settings must be set via ENV such as [**Persistent Directories**](./?#persistent-directories) for config/data/log directories. ::: ```shell JELLYFIN_APIKEY=c9fae8756fbf481ebd9c5bb56bd6540c JELLYFIN_URL=192.168.0.101:8096 JELLYFIN_USER=MyUser MALOJA_URL="http://domain.tld" node src/index.js ```
`./config/config.json` ```json title="./config/config.json" { "sources": [ { "type": "jellyfin", "clients": ["myConfig"], "name": "myJellyfinSource", "data": { "apiKey": "a89cba1569901a0671d5a9875fed4be1", "url": "http://192.168.0.101:8096", "user": "MyUser" } } ], "clients": [ { "type": "maloja", "name": "myConfig", "data": { "url": "http://localhost:42010", "apiKey": "myMalojaKey" } } ], } ```
```shell npm run start ```
:::tip The web UI and API is served on port `9078`. This can be modified using the `PORT` environmental variable. ::: ## Persistent Directories The directories MS uses for * **Configuration** - `config.json`, `jellyfin.json`, etc... * **Data** - database, cache, etc... * **Logs** can be specified by environmental variables passed directly to `npm`/`node`, or set in an `.env` file in the working directory. Settings these paths is *optional.* If you do not set paths MS will try to use OS-standardized directories, falling back to subfolders in the working directory (`.config/`). **Note: These paths are automatically set for you when using Docker.** When parsing these ENVs MS will resolve relative directories but *not* bash expansions like `~` for home. Examples: * `CONFIG_DIR=/my/absolute/path` => sets directory to use for config files * `DATA_DIR=./relative/data` => sets directory relative to working directory for data files * `LOGS_DIR=~/myDir/logs` => ❌ cannot use this path! (The bash expansions shown below are for example only) All of your configuration files, like `config.json`, `jellyfin.json`, etc... will be read from this directory. Order of path acquisition: * `$CONFIG_DIR` - user-defined (or auto defined in Docker image) * `$CONFIGURATION_DIRECTORY` - defined by [systemd](/installation/service) * OS-standardized directory from below... `$XDG_CONFIG_HOME/multi-scrobbler` or `~/.config/multi-scrobbler` `~/Library/Preferences/multi-scrobbler` `%APPDATA%\multi-scrobbler\Config` All of the persistent data -- like the database (`ms.db`), cache, and credential files -- will be written to this directory. Order of path acquisition: * `$DATA_DIR` - user-defined (or auto defined in Docker image) * `$STATE_DIRECTORY` - defined by [systemd](/installation/service) * OS-standardized directory from below... `$XDG_DATA_HOME/multi-scrobbler` or `~/.local/share/multi-scrobbler` `~/Library/Application Support/multi-scrobbler` `%LOCALAPPDATA%\multi-scrobbler\Data` Logs will be written to this directory. Order of path acquisition: * `$LOGS_DIR` - user-defined (or auto defined in Docker image) * `$LOGS_DIRECTORY` - defined by [systemd](/installation/service) * OS-standardized directory from below... `$XDG_STATE_HOME/multi-scrobbler` or `~/.local/state/multi-scrobbler` `~/Library/Logs/multi-scrobbler` `%LOCALAPPDATA%\multi-scrobbler\Log`