Mopidy is a music server which can play music both from multiple sources, like your local hard drive, radio streams, and from Spotify and SoundCloud. Searches combines results from all music sources, and you can mix tracks from all sources in your play queue. Your playlists from Spotify or SoundCloud are also available for use.
The mopidy command is used to start the server.
Show help message and exit.
Show Mopidy’s version number and exit.
Show less output: warning level and higher.
Show more output. Repeat up to 3 times for even more.
Save debug log to the file specified in the logging/debug_file config value, typically ./mopidy.log.
Specify config file to use. To use multiple config files, separate them with a colon. The later files override the earlier ones if there’s a conflict.
Specify additional config values in the section/key=value format. Can be provided multiple times.
Show the current effective config. All configuration sources are merged together to show the effective document. Secret values like passwords are masked out. Config for disabled extensions are not included.
Show dependencies, their versions and installation location.
Additionally, extensions can provide extra commands. Run mopidy –help for a list of what is available on your system and command-specific help. Commands for disabled extensions will be listed, but can not be run.
Clear local media files from the local library.
Scan local media files present in your library.
To start the music server, run:
mopidy
To start the server with an additional config file than can override configs set in the default config files, run:
mopidy --config ./my-config.conf
To start the server and change a config value directly on the command line, run:
mopidy --option mpd/enabled=false
The --option flag may be repeated multiple times to change multiple configs:
mopidy -o mpd/enabled=false -o spotify/bitrate=320
The mopidy config output shows the effect of the --option flags:
mopidy -o mpd/enabled=false -o spotify/bitrate=320 config
Report bugs to Mopidy’s issue tracker at <https://github.com/mopidy/mopidy/issues>