SeanBurlington wrote: > I'm developing the app in ReactJS - which provides a proxy for > development - and the next step was to test it as an installable PWA - > which requires https and a valid cert so I used apache as a proxy for > that too. > Docker isn't intended as a distribution mechanism - it just seemed > easier than describing how to setup a proxy - and > (I'm assuming you meant web server and not proxy?) Well, the question is if you want an average LMS user to be able to install it. With a plugin, that's a realistic prospect. With having to install/configure/run a web server (and maybe even get a ssl cert) and deploy the app to it, probably not so much.
> > I don't know how to make it a plugin (I have looked for docs but some > are outdated - and it's been 20 years since I wrote any non-trivial > Perl) > That's why I mentioned Material and extGUI4LMS, which both take the approach I described. You can just copy/paste/adapt the relevant parts. > > I have to admit that despite being a user for a decade LMS has more > features than I knew - have I also missed per user favourites lists ? > No, but you can (persistently) save plugin preferences, which your app could map to users. > > Yes - that's what I'm thinking. > LMS offers *so much* functionality that exposing it via the web would be > a significant risk. > Exposing via a proxy which only allows a subset of functionality > (perhaps just browse and download MP3) would mean that even if user > login was hacked - all that would gain is access to data and a possible > DOS attack. > But it would be much harder in such a system to gain code execution. > Not sure what architecture you have in mind, but this subset of functionality would have to be severely restricted (e.g. a plugin I've seen registers a LMS server command which allows to execute any system command on the LMS server) > > Web apps have a lot more power than they used to. > It is possible to store significant amounts of data in places like > indexdb > Not the whole of a collection - but enough to be useful. > I'm aware of indexdb (although the file systems API may be a better fit for this use case (provided it actually works in the current browsers)) I was thinking about the issues of synchronizing in general (e.g how would the app notice that a file has changed / has been deleted on the server etc.) Even if the app just just downloads some manually selected albums, there'd have to be some admin UI to e.g. delete local data At this point, personally, I'd just install syncthing instead and be done with it. 'Various SW' (https://www.nexus0.net/pub/sw/): Web Interface | TUI | Playlist Editor / Generator | Music Classification | Similar Music | Announce | EventTrigger | Chiptunes | LMSlib2go | ... 'Various HowTos' (https://www.nexus0.net/pub/documents/LMS/): build a self-contained LMS | Bluetooth/ALSA | Control LMS with any device | ... ------------------------------------------------------------------------ Roland0's Profile: http://forums.slimdevices.com/member.php?userid=56808 View this thread: http://forums.slimdevices.com/showthread.php?t=113262 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
