mirror of
https://github.com/beetbox/beets.git
synced 2025-12-06 16:42:42 +01:00
A little fiddling with embyupdate
Clean up some wording w/r/t efbd58cd55.
This commit is contained in:
parent
d992221853
commit
c9ec5e411c
3 changed files with 4 additions and 3 deletions
|
|
@ -153,7 +153,7 @@ class EmbyUpdate(BeetsPlugin):
|
||||||
u'host': u'http://localhost',
|
u'host': u'http://localhost',
|
||||||
u'port': 8096,
|
u'port': 8096,
|
||||||
u'apikey': None,
|
u'apikey': None,
|
||||||
u'password': None
|
u'password': None,
|
||||||
})
|
})
|
||||||
|
|
||||||
self.register_listener('database_change', self.listen_for_db_change)
|
self.register_listener('database_change', self.listen_for_db_change)
|
||||||
|
|
|
||||||
|
|
@ -47,7 +47,8 @@ Fixes:
|
||||||
:bug:`2302`
|
:bug:`2302`
|
||||||
* :doc:`/plugins/lyrics`: The plugin now reports a beets-specific User-Agent
|
* :doc:`/plugins/lyrics`: The plugin now reports a beets-specific User-Agent
|
||||||
header when requesting lyrics. :bug:`2357`
|
header when requesting lyrics. :bug:`2357`
|
||||||
* :doc:`/plugins/embyupdate`: Fix a bug that apikey and password is needed in config.
|
* :doc:`/plugins/embyupdate`: The plugin now checks whether an API key or a
|
||||||
|
password is provided in the configuration.
|
||||||
|
|
||||||
For plugin developers: new importer prompt choices (see :ref:`append_prompt_choices`), you can now provide new candidates for the user to consider.
|
For plugin developers: new importer prompt choices (see :ref:`append_prompt_choices`), you can now provide new candidates for the user to consider.
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -3,7 +3,7 @@ EmbyUpdate Plugin
|
||||||
|
|
||||||
``embyupdate`` is a plugin that lets you automatically update `Emby`_'s library whenever you change your beets library.
|
``embyupdate`` is a plugin that lets you automatically update `Emby`_'s library whenever you change your beets library.
|
||||||
|
|
||||||
To use ``embyupdate`` plugin, enable it in your configuration (see :ref:`using-plugins`). Then, you'll probably want to configure the specifics of your Emby server. You can do that using an ``emby:`` section in your ``config.yaml``, which looks like this::
|
To use ``embyupdate`` plugin, enable it in your configuration (see :ref:`using-plugins`). Then, you'll want to configure the specifics of your Emby server. You can do that using an ``emby:`` section in your ``config.yaml``, which looks like this::
|
||||||
|
|
||||||
emby:
|
emby:
|
||||||
host: localhost
|
host: localhost
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue