From aa9fde4dd9c96cace89ae689ffaf385fbd13fd26 Mon Sep 17 00:00:00 2001 From: Leonid Bogdanov Date: Mon, 17 Sep 2018 09:19:27 +1000 Subject: [PATCH 1/4] Add Yandex.Disk backend --- docs/ext/backends.rst | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/ext/backends.rst b/docs/ext/backends.rst index 7299cc98..74c04fb4 100644 --- a/docs/ext/backends.rst +++ b/docs/ext/backends.rst @@ -252,6 +252,15 @@ Provides a backend for playing music from the `VKontakte social network `_. +Mopidy-YDisk +============ + +https://github.com/vonZeppelin/mopidy-ydisk + +Provides a backend for playing music from `Yandex.Disk cloud storage +`_. + + Mopidy-YouTube ============== From 4f8b755a2abaeae4fe69b6681627c3bfab4a1dc3 Mon Sep 17 00:00:00 2001 From: Nick Steel Date: Mon, 8 Oct 2018 17:24:59 +0100 Subject: [PATCH 2/4] docs: update curl HTTP POST example Must set 'Content-Type: application/json' header due to #1668 --- docs/api/http.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/api/http.rst b/docs/api/http.rst index f2a50b27..56b72dc1 100644 --- a/docs/api/http.rst +++ b/docs/api/http.rst @@ -25,7 +25,7 @@ to listen to events, you should probably use the WebSocket API instead. Example usage from the command line:: - $ curl -d '{"jsonrpc": "2.0", "id": 1, "method": "core.playback.get_state"}' http://localhost:6680/mopidy/rpc + $ curl -d '{"jsonrpc": "2.0", "id": 1, "method": "core.playback.get_state"}' http://localhost:6680/mopidy/rpc -H 'Content-Type: application/json' {"jsonrpc": "2.0", "id": 1, "result": "stopped"} For details on the request and response format, see :ref:`json-rpc`. From 043da0e8716da7b28d32e8ed6f6e1a72793a3220 Mon Sep 17 00:00:00 2001 From: Nick Steel Date: Mon, 8 Oct 2018 17:38:39 +0100 Subject: [PATCH 3/4] docs: mention required Content-Type header --- docs/api/http.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/api/http.rst b/docs/api/http.rst index 56b72dc1..b9f807e3 100644 --- a/docs/api/http.rst +++ b/docs/api/http.rst @@ -19,7 +19,8 @@ HTTP POST API The Mopidy web server accepts HTTP requests with the POST method to http://localhost:6680/mopidy/rpc, where the ``localhost:6680`` part will vary -with your local setup. The HTTP POST endpoint gives you access to Mopidy's +with your local setup. Your requests must also set the Content-Type header to +application/json. The HTTP POST endpoint gives you access to Mopidy's full core API, but does not give you notification on events. If you need to listen to events, you should probably use the WebSocket API instead. From 0bc458cadea30c3006993b9c9f79fa4337440a28 Mon Sep 17 00:00:00 2001 From: Stein Magnus Jodal Date: Tue, 9 Oct 2018 00:25:44 +0200 Subject: [PATCH 4/4] docs: Minor tweaks --- docs/api/http.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/api/http.rst b/docs/api/http.rst index b9f807e3..4c4f9506 100644 --- a/docs/api/http.rst +++ b/docs/api/http.rst @@ -19,14 +19,14 @@ HTTP POST API The Mopidy web server accepts HTTP requests with the POST method to http://localhost:6680/mopidy/rpc, where the ``localhost:6680`` part will vary -with your local setup. Your requests must also set the Content-Type header to -application/json. The HTTP POST endpoint gives you access to Mopidy's +with your local setup. Your requests must also set the ``Content-Type`` header +to ``application/json``. The HTTP POST endpoint gives you access to Mopidy's full core API, but does not give you notification on events. If you need to listen to events, you should probably use the WebSocket API instead. Example usage from the command line:: - $ curl -d '{"jsonrpc": "2.0", "id": 1, "method": "core.playback.get_state"}' http://localhost:6680/mopidy/rpc -H 'Content-Type: application/json' + $ curl -d '{"jsonrpc": "2.0", "id": 1, "method": "core.playback.get_state"}' -H 'Content-Type: application/json' http://localhost:6680/mopidy/rpc {"jsonrpc": "2.0", "id": 1, "result": "stopped"} For details on the request and response format, see :ref:`json-rpc`.