Your library.
Your server.

Clone the repository and create the music folder. Edit .env: MUSIC_DIR is the folder with your music and PUBLIC_URL is the origin your apps connect to, for example https://music.yourdomain.com, without /api/v1.

git clone https://github.com/mateodd1/DoubleMusic.git
cd DoubleMusic
cp .env.example .env
mkdir -p music

Start it with the prebuilt image:

docker compose -f compose.release.yml pull
docker compose -f compose.release.yml up -d

Create your account. Type the password in your terminal; it will not stay in your shell history:

read -r -s -p 'Password: ' MUSIC_PASSWORD; printf '\n'
printf '%s\n' "$MUSIC_PASSWORD" | docker compose -f compose.release.yml exec -T doublemusic node cli.js add admin --admin --password-stdin
unset MUSIC_PASSWORD

No access to the registry from the server? Load the downloaded archive, verifying its checksum first:

sha256sum --check SHA256SUMS --ignore-missing
docker load -i doublemusic_*_linux_amd64.docker.tar.gz
DOUBLEMUSIC_IMAGE=doublemusic:1.4.1 docker compose -f compose.release.yml up -d --pull never

Install the package with apt, which resolves FFmpeg and the dependencies. On ARM64 machines use arm64 instead of amd64.

sha256sum --check SHA256SUMS --ignore-missing
sudo apt install ./doublemusic_*_amd64.deb

The service is created but does not start on its own: configure it and create an account first. Edit /etc/doublemusic/doublemusic.env and set PUBLIC_URL to the origin your clients use, without /api/v1. Put your music in /srv/doublemusic/music or in the folder set in MUSIC_DIR; the service cannot read /home, so use /srv or /mnt. It listens on 127.0.0.1:3000: put an HTTPS proxy in front, or use HOST=0.0.0.0 to expose it on your network.

read -r -s -p 'Password: ' MUSIC_PASSWORD; printf '\n'
printf '%s\n' "$MUSIC_PASSWORD" | sudo -u doublemusic doublemusic-user add admin --admin --password-stdin
unset MUSIC_PASSWORD
sudo systemctl enable --now doublemusic.service
sudo systemctl status doublemusic.service

Install the package with dnf. It needs FFmpeg (on Fedora, ffmpeg-free); other RPM distributions need a compatible provider and their repositories enabled. On ARM64 use aarch64. Then configure and start the service as on Debian and Ubuntu.

sha256sum --check SHA256SUMS --ignore-missing
sudo dnf install ./doublemusic-*.x86_64.rpm

If you prefer to build it yourself, use the repository docker-compose.yml, which builds the image on your machine:

docker compose up -d --build

In the app, enter the same URL as PUBLIC_URL and sign in with that account. Your HTTPS proxy must forward every route to the service, including Connect WebSocket connections.

Music is mounted read-only. With Docker, the library-data volume stores accounts, personal libraries, the index and the cache; with packages, /var/lib/doublemusic.

In the JSON file pointed to by SOURCES_FILE you choose whether to use the local library, external connections or both. Turning off the library skips scanning; turning off external connections prevents loading their credentials or querying them. Your files, accounts and personal libraries are kept.

{
  "version": 1,
  "library": { "enabled": true },
  "external": { "enabled": false }
}

With Docker, mount it by creating compose.config.yml and applying it with docker compose -f compose.release.yml -f compose.config.yml up -d --force-recreate doublemusic. With packages, edit /etc/doublemusic/settings.json. The modules guide explains the contract for external connections.

services:
  doublemusic:
    environment:
      SOURCES_FILE: /config/settings.json
    volumes:
      - ./settings.json:/config/settings.json:ro

Accounts are managed from the server terminal. add and passwd read the password from standard input, as when creating it.

docker compose -f compose.release.yml exec doublemusic node cli.js list
docker compose -f compose.release.yml exec doublemusic node cli.js revoke username
docker compose -f compose.release.yml exec -T doublemusic node cli.js passwd username --password-stdin
docker compose -f compose.release.yml exec doublemusic node cli.js del username
docker compose -f compose.release.yml logs --tail=100 doublemusic

sudo -u doublemusic doublemusic-user list
sudo -u doublemusic doublemusic-user revoke username
sudo -u doublemusic doublemusic-user passwd username --password-stdin
sudo -u doublemusic doublemusic-user del username
sudo -u doublemusic doublemusic-server --healthcheck
sudo journalctl -u doublemusic.service -n 100 --no-pager

Upgrading. With Docker, change the image tag (DOUBLEMUSIC_IMAGE), pull it and recreate the service with the same volumes. With packages, install the new one: configuration, accounts, sessions and personal libraries are preserved.

Backups. For a consistent backup, stop the service and copy the library-data volume (Docker) or /var/lib/doublemusic (packages). Back up your music folder separately. Removing or purging the package keeps your music and data.