The remote was a very low priority and was just a thought. PlexConnect has cgi in the python code already. My main concentration here was to get a cgi front-end to update the main code on demand on all platforms using any web-bowser on any device local or remote from the plexconnect host. It’s for OSX only at this time but could be cross platform compliant if desired/coded to do so. This is why I showed the cgi first and said the other was how I came up with the idea. As I said you can do a lot with cgi pick your poison as in features. 
The problem with updating in general for most users is they don’t clone the git or install git to begin with per the readme.md on @baa’s github. What do you do about those users? Let’s just say you had a cgi built-in to plexconnect as a front-end. With this I would imagine you could stop the code/update/restart the code. But what do you do about users that run Linux, Unix, Windows, and OSX and have a auto starting way of running plexconnect such as a plist, .bat, or something else? How do you terminate that process to update? There is a lot of variables in play but I would imagine if you could stop the code within itself/update/start the code using a cgi or something else it could be possible. As for a automatic git pull at startup that would be tough unless everyone was on board with cloning and git.
@whalman.j good going! I thought the remote was webconnect. Anyway! My badd!
Just a thought, if your looking for how user friendly your or any app is, a easy way is to count the clicks! i.e. how many clicks doe it take to get your app going! Count everything, documentation and read me's is not the point. Apache, git, python, PlexConnect, copy, paste. Count everything.
Now, once you've done that, count how many clicks it takes for launchctl daemon on OSX(I use this example since your app, as you mentioned only supports OSX at the moment)or any other current method available, takes to install and get PlexConnect going.
The software you create should require less clicks/effort than the original. I'm not talking about features!
Sorry to all following this thread, I know what I am posting is off topic.
Good luck!
There is topics for that discussion 
feel free to post in here and I will answer your question. I would hate to go off topic in this topic.
https://forums.plex.tv/topic/95260-openconnect-osx-app/
Also most of what you are asking I have answered already in here as to why it’s a better way to go counting all the “clicks” as opposed to other methods to eliminate terminal work completely after my app is installed. Git is required regardless of any app for updates. Apache is only needed for webconnect not openconnect. Python, well thats required regardless for plexconnect to function so I dont see how you can even count that.
https://forums.plex.tv/topic/99162-plexify-discussion/
@get.jakey - I do agree with you, but Rome wasn't build in one day ;) I takes time and the right decisions.
Like the stuff that is behind Plex itself, is because there are more developers + some budget and PlexWeb was already available so implementing ChromeCast was not like reinventing the wheel or builing from scratch. But it took Plex 3+ years to get to this point.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
