docs: describe the library update steps
This commit is contained in:
parent
10b0796bbd
commit
dd6e8c0f77
@ -13,6 +13,20 @@ 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
|
accept connections by any MPD client. Check out our non-exhaustive
|
||||||
:doc:`/clients/mpd` list to find recommended clients.
|
:doc:`/clients/mpd` list to find recommended clients.
|
||||||
|
|
||||||
|
Updating the library
|
||||||
|
====================
|
||||||
|
|
||||||
|
To update the library, e.g. after audio files have changed, run::
|
||||||
|
|
||||||
|
mopidy local scan
|
||||||
|
|
||||||
|
Afterwards, to refresh the library (which is for now only available
|
||||||
|
through the API) it is necessary to run::
|
||||||
|
|
||||||
|
curl -d '{"jsonrpc": "2.0", "id": 1, "method": "core.library.refresh"}' http://localhost:6680/mopidy/rpc
|
||||||
|
|
||||||
|
This makes the changes in the library visible to the clients.
|
||||||
|
|
||||||
|
|
||||||
Stopping Mopidy
|
Stopping Mopidy
|
||||||
===============
|
===============
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user