Re: When developing a plugin, where should I put it in the Docker container?

Here is how I do it (which I know Michael does not endorse) but it would
have avoided the problem you have hit.

I make a genuine repo XML file and host it somewhere private that LMS
can access (and I sometimes give that URL to beta testers).
Then I make a real plugin (a skeleton is enough) and install it using
the Settings/Plugin mechanism via the custom repo.

Then I work on the code and simply transfer it to the installation
location without updating the install.xml (my LMS is running on a
Raspberry Pi but my development is on Windows).
Then a simple stop/start of LMS (sometimes needs to be started twice
because it quits without an error message) and the new code is up and
running.

Eventually I decide that my updates are worth calling a beta release so
I update the install.xml version number and the repo xml version number,
file pointer & checksum and perform a real update with LMS. This also
helps me check that the packaging is right which is useful for when
preparing a real release.

For version numbering I put a letter after the numbers ... so it goes
1, 2a, 2b, 2c, 2, 3a, 3b, 3
with 1, 2 and 3 being the official releases and the ones with letters at
the end as the beta of what will become the official release.

Of course, a proper change control system and automated builds would be
much more professional - but I have not invested the time to do that.



Paul Webster
author of \"now playing\" plugins covering radio france (fip etc),
planetradio (bauer - kiss, absolute, scala, jazzfm etc), kcrw, abc
australia and cbc/radio-canada
and, via the extra \"radio now playing\" plugin lots more - see
https://forums.slimdevices.com/showthread.php?115201-announce-radio-now-playing-plugin
------------------------------------------------------------------------
Paul Webster's Profile: http://forums.slimdevices.com/member.php?userid=105
View this thread: http://forums.slimdevices.com/showthread.php?t=116387