3.Party Devs and Hook into the WebServer

Feature Suggestions
1

When looking @ http://:32400 you see the relevant uri's that the PMS accept.

 

Would be so cool, if one was added name "'3Party", that pointed to a Library/Plug-Ins/3Party directory

 

And that this directory was excluded from AutoUpdate

 

That way, a 3.Party bundle could create a Symbolic link in there, pointing to an http directory below it's own bundle directory.

 

And by doing so, a 3.Party channel could start to use jscript and fancy http to create a nice interface.

 

To grasp an idea of what I'm talking about, take a peak here:

 

https://forums.plex.tv/topic/126254-rel-webtools/

 

Above works nicely on Linux flavours, but sadly not on Windows.

 

And to follow up on this....If it was possible to create a directory object in a channel, that when clicked on, would be a redirect to an URL

 

Hope it makes sense, and would make Plex 3.Party standout compared to like XBMC plug-ins

 

Best Regards

 

Tommy

2

This would put the security of a Plex installation in the hands of the plugin devs… Not something I would be very comfortable with.

Yeah, I know that I could just avoid plugins of this type but I doubt many users would be aware of the risk.

3

This would put the security of a Plex installation in the hands of the plugin devs.... Not something I would be very comfortable with.
Yeah, I know that I could just avoid plugins of this type but I doubt many users would be aware of the risk.

How is this any different than ordinary plug-in's?

All I want, is a better web-interface for the channels

And it still would follow the auth. of Plex

/T

4

How is this any different than ordinary plug-in's?

Ordinary plugins cannot be accessed from the outside. If you hook into the http server it would be directly exposed to the internet. At least if I have understood your request correctly :)

EDIT: Guess I was wrong. As your WebTools bundle shows outside access to plugins is possible in it's current form as well. Not that it makes it less disturbing ;)

5

Isn’t that only if you have 32400 exposed?

6

Ordinary plugins cannot be accessed from the outside. If you hook into the http server it would be directly exposed to the internet. At least if I have understood your request correctly :)

EDIT: Guess I was wrong. As your WebTools bundle shows outside access to plugins is possible in it's current form as well. Not that it makes it less disturbing ;)

The Webtools bundle is exposed the same way as other bundles.....via port 32400

And access to is is controlled via the build in access control of PMS!

If you restrict access to PMS, then WebTools can't access anything.

Only difference between that and an ordinary bundle is the fact, that part of it live outside the channel container, but still within the webserver from Plex.

And as you can see, me and dagalufh already made it work, but is struggling with the http part on the windows platform, so looking for a work around for that.

/Tommy