I've updated PMS several times over the last year, but upon a recent fresh install of my ATV3 and Plex, it occurs to me that I never updated the PlexConnect side of things. It that advisable to do that from time to time?
It is as simple as downloading the latest master code and replacing that extracted folder with the existing one in Applications? I understand the certs have been placed in the assets folder there, so that's something that I suppose must remain. Just wondering if I missed a thread with a good rundown of the update procedure.
Depends on the OS. If you properly cloned the github with git you can simply navigate to the PlexConnect base dir and type:
git pull
If using OSX you can use OpenPlex to update manually or install a auto update plist to keep PlexConnect up to date by checking github every 6 hours and only performing a update if a new commit (update) is available all automatically. You just need to exit the hijacked app to complete the process each time a update has occurred.
I'm rookie enough that you're talking Greek to me there :) I can copy and paste Terminal commands, but I haven't gone beyond that. I'm sure Plex and its components is the most challenging thing I've done so far. Starting over this time, I'm sure I'll pick up a few lessons. Git is certainly new to me though. I was just wondering if there was a good guide written for updating every once in a while (even if it is a long step by step list).
I actually tried OpenPlex last night when I was doing my "from scratch" reinstall. It hung on the very first step... so I eventually gave up and went back to the "manual" install instructions that worked for me a year ago when I first did it. Compared to the successful final install this time, I noticed that OpenPlex must've come close, but not quite completed the PlexConnect-master folder. I'm sure it's useful, but it wasn't for me this time.
I'm on Mac, living dangerously now with the latest Yosemite beta 5, given that they're very close to the finish line. Until recently I was on Mavericks.
OpenPlex git clones to Applications/PlexConnect not PlexConnect-master. If you want me to debug that issue you can click my name and send me a PM. Otherwise you can type this in a teminal window:
git
If it prompts you to install command line tools install them. Otherwise do this after you reboot or kill plexconnect cleanly (assuming you don’t have the bash plist installed also if there is a PlexConnect Folder in /Appliactions delete it first):
It should say up to date. OpenPlex automates all this and eliminates terminal all together but that’s if something isn’t wrong with the OS. From that point forward if you are still doing everything manually this is how to properly update (again assuming your don’t have the bash plist installed):
@krollins, regarding your other question "when to upgrade PlexConnect" I would like to share with you the following: The developers (Baa/Roidy) are making a superb job assuring that updates to Git have good quality. But Git is used not only for stable releases but also for "beta" ones.
When you update PlexConnect using the git pull method you will get the latest release, and very probably you will get a "beta" one. So there is always a risk (past experience shows that this is a small risk) that you will will get unstable code.
Being a newbie myself, let me share with you what I'm doing to be on the "safe side":
My initial installation of PlexConnect is always a "stable" release. I'm lucky to be a Synology user and bwynants publishes the stable releases for that platform. For other platforms you would probably have to read the PlexConnect changelog to identify which stable release best suits you needs, create a zip and install PlexConnect from it
Before using the git pull method I always make a backup of the plexconnect folder with a different name. This way I can always go back if git pull brings a release with unacceptable bugs
