Mopidy3

Mopidy3 is an Unraid Docker template that packages Mopidy, an extensible Python music server, with pre-loaded support for Spotify, YouTube, and snapcast…

  • Media Applications
  • Media Servers
  • Other
  • Tools & Utilities
Mopidy3 is an Unraid Docker template that packages Mopidy, an extensible Python music server, with pre-loaded support for Spotify, YouTube, and snapcast streaming plus automatic multi-instance management.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

10/100 Low

Maintained
0last commit 1003 days ago
Popular
61 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 31 days ago

GitHub stars
1
Open issues
0
Last commit
2024-02-22
License
MIT
Activity
stale

Checked 9 days ago - source: GitHub (daredoes/docker-mopidy3)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Volume mounts and ports Set up a volume mount from /mnt/user/appdata/mopidy/ to /config/ inside the container. Add TCP ports for MPD (6680), HTTP (6600), and audio output (4953). For additional instances, add extra port pairs. source
  • Configuration A basic configuration is autogenerated. The template is located at /etc/mopidy inside the container. Do not modify the audio output port setting (port=4953), as it is automatically replaced for each generated instance. source
  • Docker run setup The README shows host-network runs, or explicit ports 9001, 6680, 6600, and 4953; map a music folder to /media and Mopidy data to /home/.local/share/mopidy. source
  • Container paths and ports Mount your music folder to /media and Mopidy's data directory to /home/.local/share/mopidy; use host networking or publish ports 9001 (Iris web UI), 6680, 6600, and 4953. source
  • Run Mopidy3 Run the container in host mode or expose ports 9001, 6680, 6600, and 4953, mounting /media for music and /home/.local/share/mopidy for data. source

Fetched 32 days ago - each note links to its source

Alternatives (3)

  • Airsonic - Airsonic is a Free and Open Source community driven media server which allows you to stream, transcode, manage, and share your personal aud…
  • Funkwhale - Open-source, self-hosted streaming platform supports Android, iOS, podcasts, uploads, sharing, no ads or tracking, federated across decentr…
  • Subsonic - Subsonic is a free, web-based media streamer, providing ubiquitous access to your music and video.

Checked 40 days ago - source: AlternativeTo

Common questions

Which ports should I expose for the Mopidy3 container?

Expose 9001 for Supervisor, plus 6680, 6600, and 4953. The README's non-host example maps those four ports.

Which host directories should I bind mount?

Map your music directory to /media and Mopidy's internal data to /home/.local/share/mopidy. The README examples use /music for music and /data for the internal data path.

How are multiple Mopidy instances configured?

The entrypoint creates a Supervisord configuration for each server in servers.json, with unique environment variables per instance. Startup removes matching Snapcast streams and sends Snapcast stream information for synchronized playback.

Can I install extra Python plugins for Mopidy?

The start script installs Python packages listed in requirements.txt. The file path is specified by the REQUIREMENTS_FILE environment variable.

What should I be careful about when editing mopidy.conf?

Configuration problems can lead to connectivity issues. The README warns to be cautious when modifying mopidy.conf.

Answers sourced from github.com

Community

Collected 53 days ago - public community threads