> I am looking to use Docker to create an image of my LMS installation on
> a Raspberry Pi but as part of this I would like to include the
> installation of the plugins I use such as Triode's Spotify plugin. If
> this possible?
There is no documented way to do this. But I'm sure it can be done
_some_ way.
a.) create a script to download and unzip the plugin file to the
installation's Plugins folder. Disadvantage: it won't use LMS'
auto-update feature. It probably would even cause confusion if LMS tried
to update it, but failed to do so.
b.) write a script to create an initial plugins/state.prefs (I think),
which would be pre-set with the "need-install" flags for whatever plugin
you want LMS to install. There's no docs for this, of course, and even
the file and flag name I just mentioned might be wrong. But we could
figure this one out.
The latter option probably is the better approach, as it would allow to
use LMS' plugin manager to handle the actual installation and updates.
But it's reaching deep into the plugin manager's configuration.
> If it isn't, can anyone tell me where the plugin configuration and
> installs live on disk so I could look at manually copying them in as
> part of the Dockerfile setup?
Check out a running installation: Settings/Information. There's a paths
section which would show you where prefs are stored. That's where there
should be state.prefs or similar file with flags for every plugin you
try to install/update whatever. Best chose some plugin to install on a
running LMS. Then shut down LMS and check the values in that file. Write
a script to create those values upon image installation.
--
Michael
> a Raspberry Pi but as part of this I would like to include the
> installation of the plugins I use such as Triode's Spotify plugin. If
> this possible?
There is no documented way to do this. But I'm sure it can be done
_some_ way.
a.) create a script to download and unzip the plugin file to the
installation's Plugins folder. Disadvantage: it won't use LMS'
auto-update feature. It probably would even cause confusion if LMS tried
to update it, but failed to do so.
b.) write a script to create an initial plugins/state.prefs (I think),
which would be pre-set with the "need-install" flags for whatever plugin
you want LMS to install. There's no docs for this, of course, and even
the file and flag name I just mentioned might be wrong. But we could
figure this one out.
The latter option probably is the better approach, as it would allow to
use LMS' plugin manager to handle the actual installation and updates.
But it's reaching deep into the plugin manager's configuration.
> If it isn't, can anyone tell me where the plugin configuration and
> installs live on disk so I could look at manually copying them in as
> part of the Dockerfile setup?
Check out a running installation: Settings/Information. There's a paths
section which would show you where prefs are stored. That's where there
should be state.prefs or similar file with flags for every plugin you
try to install/update whatever. Best chose some plugin to install on a
running LMS. Then shut down LMS and check the values in that file. Write
a script to create those values upon image installation.
--
Michael