91 lines
3.0 KiB
ReStructuredText
91 lines
3.0 KiB
ReStructuredText
********
|
|
Settings
|
|
********
|
|
|
|
Mopidy reads settings from the file ``~/.mopidy/settings.py``, where ``~``
|
|
means your *home directory*. If your username is ``alice`` and you are running
|
|
Linux, the settings file should probably be at
|
|
``/home/alice/.mopidy/settings.py``.
|
|
|
|
You can either create this file yourself, or run the ``mopidy`` command, and it
|
|
will create an empty settings file for you.
|
|
|
|
|
|
Music from Spotify
|
|
==================
|
|
|
|
If you are using the Spotify backend, which is the default, enter your Spotify
|
|
Premium account's username and password into the file, like this::
|
|
|
|
SPOTIFY_USERNAME = u'myusername'
|
|
SPOTIFY_PASSWORD = u'mysecret'
|
|
|
|
|
|
Music from local storage
|
|
========================
|
|
|
|
If you want use Mopidy to play music you have locally at your machine instead
|
|
of using Spotify, you need to change the backend from the default to
|
|
:mod:`mopidy.backends.local` by adding the following line to your settings
|
|
file::
|
|
|
|
BACKENDS = (u'mopidy.backends.local.LocalBackend',)
|
|
|
|
You may also want to change some of the ``LOCAL_*`` settings. See
|
|
:mod:`mopidy.settings`, for a full list of available settings.
|
|
|
|
.. note::
|
|
|
|
Currently, Mopidy supports using Spotify *or* local storage as a music
|
|
source. We're working on using both sources simultaneously, and will
|
|
hopefully have support for this in the 0.3 release.
|
|
|
|
|
|
Generating a tag cache
|
|
----------------------
|
|
|
|
Previously the local storage backend relied purely on ``tag_cache`` files
|
|
generated by the original MPD server. To remedy this the command
|
|
:command:`mopidy-scan` has been created. The program will scan your current
|
|
:attr:`mopidy.settings.LOCAL_MUSIC_FOLDER` and build a MPD compatible
|
|
``tag_cache``.
|
|
|
|
To make a ``tag_cache`` of your local music available for Mopidy:
|
|
|
|
#. Ensure that :attr:`mopidy.settings.LOCAL_MUSIC_FOLDER` points to where your
|
|
music is located. Check the current setting by running::
|
|
|
|
mopidy --list-settings
|
|
|
|
#. Scan your music library. Currently the command outputs the ``tag_cache`` to
|
|
``stdout``, which means that you will need to redirect the output to a file
|
|
yourself::
|
|
|
|
mopidy-scan > tag_cache
|
|
|
|
#. Move the ``tag_cache`` file to the location
|
|
:attr:`mopidy.settings.LOCAL_TAG_CACHE` is set to, or change the setting to
|
|
point to where your ``tag_cache`` file is.
|
|
|
|
#. Start Mopidy, find the music library in a client, and play some local music!
|
|
|
|
|
|
Connecting from other machines on the network
|
|
=============================================
|
|
|
|
As a secure default, Mopidy only accepts connections from ``localhost``. If you
|
|
want to open it for connections from other machines on your network, see
|
|
the documentation for :attr:`mopidy.settings.MPD_SERVER_HOSTNAME`.
|
|
|
|
|
|
Scrobbling tracks to Last.fm
|
|
============================
|
|
|
|
If you want to submit the tracks you are playing to your `Last.fm
|
|
<http://www.last.fm/>`_ profile, make sure you've installed the dependencies
|
|
found at :mod:`mopidy.frontends.lastfm` and add the following to your settings
|
|
file::
|
|
|
|
LASTFM_USERNAME = u'myusername'
|
|
LASTFM_PASSWORD = u'mysecret'
|