(I've made it reasonably fault tolerate of download failures/ delays.)ī. goes to github and grabs the current version of the WebTools 'bundle' (what Plex plug-ins are named). For this spk, the 'installation', if you look at 'postinst', does the following:Ī.(just like mono references 'some_program.exe' when it starts. Their 'framework' runs the plug-in, entirely under their control, at their choosing, when it's needed. All Plex plug-in modules are written in python and are invoked, under Plex's control, like any other imported python functions. Neither these urls, nor their python modules are of concern or consideration here. Plug-ins communicate with core Plex via url requests sent to Plex's port. If you look at my start script, No processes are invoked.

It makes the user, Plex, and ultimately Synology, happy, in some twisted sense of order there (haha). This package's sole purpose is to be the placeholder / 'hook' to allow you to install or remove the 'WebTools' plug-in from Plex cleanly via Package Center. You can uninstall Plex or reinstall DSM, then reinstall Plex, and the data directory will have survived intact provided the volume itself wasn't deleted.

This spk (plug-in) is 'installed', via Synology's package installation mechanism, into Plex's data directory /volume1/Plex/Library/Application Support/Plex Media Server/Plug-ins.No need to concern ourselves further with that. Their code resides in /var/packages/Plex Media Server/target. They and Syno have that level of responsibility. Plex is proprietary pre-compiled code they take care of.Sorry if I didn't explain Plex's architecture clearly enough and what I'm doing.

Installing plex on synology