Most of us on these forums know about PlexPy or it’s Perl predecessor PlexWatch/PlexWatchWeb. Many of us have asked for either of these to be integrated into the Web App in some manner, to give historical tracking information on the usage of our servers. There have been a number of requests for this integration over the last few years, and well, we’re still waiting…
Some few of us also run either PlexRequests or PlexRequests.net on their machines now, too. These apps provide the same functionality but use different core languages to do the task.
We all know about the icons across the top of the screen in the web app. For some reason the Team has decided to include a couple of them on the left in the Manage section on that pane. OK, well, I guess people couldn’t find the icon on the top of the screen? Whatever…
What I’m proposing here is a bit of a departure from previous requests about integrating these apps into the Web App. If we can’t have them fully integrated, for whatever reason, then give us a way to do our own integration. Within the Web App or Systems Settings, give us a place to point to apps on the server that we want tied in to the main Web App itself.
Under a new Manage Apps setting on Server Settings I get a place to input a Web App IP and port, and to give it a name, perhaps a default user ID, etc. Now when I step back out tot he rather clunky Discover page, under manage, I have the new app listed. I click on this new app and it opens in the “discover” window on the right side of the screen. I want to go back to the main PMS Web App, I have the left arrow at the top left corner to take me back.
We could set up 3 or 4 different Web Apps like this, depending on the systems people have set up, and can move back and forth fairly easily. While the history wouldn’t be built into the PMS DB, at least it would be accessible from the same Web App through either PlexPy or PlexWatchWeb.
Honestly, I don’t know why this type of functionality hasn’t already been built into the system.
