************** Running Mopidy ************** To start Mopidy, simply open a terminal and run:: mopidy When Mopidy says ``MPD server running at [127.0.0.1]:6600`` it's ready to accept connections by any MPD client. Check out our non-exhaustive :doc:`/clients/mpd` list to find recommended clients. To stop Mopidy, press ``CTRL+C`` in the terminal where you started Mopidy. Mopidy will also shut down properly if you send it the TERM signal, e.g. by using ``kill``:: kill `ps ax | grep mopidy | grep -v grep | cut -d' ' -f1` This can be useful e.g. if you create init script for managing Mopidy. mopidy command ============== .. program:: mopidy .. cmdoption:: --version Show Mopidy's version number and exit. .. cmdoption:: -h, --help Show help message and exit. .. cmdoption:: -q, --quite Show less output: warning level and higher. .. cmdoption:: -v, --verbose Show more output: debug level and higher. .. cmdoption:: --save-debug-log Save debug log to the file specified in the :confval:`logging/debug_file` config value, typically ``./mopidy.conf``. .. cmdoption:: --show-config 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. .. cmdoption:: --list-deps List dependencies and their versions. .. cmdoption:: --config Specify config file to use. To use multiple config files, separate them with colon. The later files override the earlier ones if there's a conflict. .. cmdoption:: -o