Updating the Plex Plugin with a button

    • OMV 3.x
    • Updating the Plex Plugin with a button

      Continuing on from here Abandoned plugins,

      Pheoxy wrote:

      So if there updates of the packages inside openmediavault-plexmediaserver for example, it doesn't automatically update to the latest version of plexmediaserver.
      How would you go about updating when a new release has been made by the developers?

      The openmediavault plugin states how on its Settings Info page but it need's editing with the base update to Jessie in OMV3.

      Original:

      Source Code

      1. Upgrading Plex Media Server Manually
      2. This will normally only have to be done by Plex Pass members upgrading to the latest packages.
      3. Command line: /etc/init.d/plexmediaserver stop
      4. Command line: cd /var/cache/apt/archives
      5. Command line: rm plex*.deb
      6. Now move the new package to this location /var/cache/apt/archives. While in the archives directory the best method is to use "wget downloadlink" from Plex forums.
      7. While on the post in the Plex forum where the package links are located right click on the 32 or 64 bit link. Then click on "Copy link address".
      8. In a Putty root session to your OMV: cd /var/cache/apt/archives
      9. Still in root session: wget(type a space after the wget then right click and paste the link. Hit ENTER and the package will download directly to this location.)
      10. Now install the package while still in archives directory: dpkg -i plex(hit TAB and then ENTER)
      11. After installation start PlexMediaServer: /etc/init.d/plexmediaserver start
      Display All

      It would need to be updated for systemctl and any other changes made.


      Source Code

      1. Upgrading Plex Media Server Manually
      2. This will normally only have to be done by Plex Pass members upgrading to the latest packages.
      3. Command line: systemctl stop plexmediaserver
      4. Command line: cd /var/cache/apt/archives
      5. Command line: rm plex*.deb
      6. Now move the new package to this location /var/cache/apt/archives. While in the archives directory the best method is to use "wget downloadlink" from Plex forums.
      7. While on the post in the Plex forum where the package links are located right click on the 32 or 64 bit link. Then click on "Copy link address".
      8. In a Putty root session to your OMV: cd /var/cache/apt/archives
      9. Still in root session: wget(type a space after the wget then right click and paste the link. Hit ENTER and the package will download directly to this location.)
      10. Now install the package while still in archives directory: dpkg -i plex(hit TAB and then ENTER)
      11. After installation start PlexMediaServer: systemctl start plexmediaserver
      Display All
      Would there be any other changes, because if there's little changes like this in documentation as well I could help out.
      You guys use Github for plugins right?

      Would it be possible to also add in this github.com/mrworf/plexupdate to the plugin with a button to update plex?

      It would be pretty handy and I'm still at beginner level but what would it involve to incorporate it like a new tab with input fields for the links instead of having to ssh in to get it done?

      It's not exactly urgent and I'm having a go at it now but advice would be nice :) .
    • Umm.. When we put a new version in the repo, you just update from the Updates tab. Why do you need something else?
      omv 4.1.15 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      Umm.. When we put a new version in the repo, you just update from the Updates tab. Why do you need something else?

      ryecoaaron wrote:

      You are better off to wait for us to put the plex update in the repo. Using the Ubuntu package is not advised.
      How do you guys go about doing that anyway? I've git cloned the plugin and edited it with the proper commands even if its not advised.

      As in how do you tell it what version of plex to grab? Because you could simplify it by just clicking a button when plexmedaserver tells you an update has come out that grabs the update that way you only have to update the plugin when plex brings out different configs and all that.
    • I manually put the package in our repo. It has nothing to do with the plugin. The plugin doesn't tell it what version to use. When you enable the plex repo in omv-extras, it enables the plex repo on our server.

      You are trying to re-create what an apt repository already does. We mirror what package is in shell.ninthgate.se. Before it goes in our repo, it is tested to work on OMV systems and with the plugin. If you allow the bleeding edge version to be installed, it may break something like the latest codec issue.
      omv 4.1.15 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      I manually put the package in our repo. It has nothing to do with the plugin. The plugin doesn't tell it what version to use. When you enable the plex repo in omv-extras, it enables the plex repo on our server.

      You are trying to re-create what an apt repository already does. We mirror what package is in shell.ninthgate.se. Before it goes in our repo, it is tested to work on OMV systems and with the plugin. If you allow the bleeding edge version to be installed, it may break something like the latest codec issue.
      So to keep it stable you wait 2 weeks or something and see what people have problems with and then include it into the plugin if its stable? I see why you would do something like that. All's I'm asking is if it's possible to make something similar to what you did with sonarr and the repository drop down menu. You could have something like a (stable) at the end of the version that's preferred and latest and previous versions included.

      It would make it easier to switch between versions if you need to and if you require the plexpass versions you would need to enter your username and password into a config on the webui so it can grab it.

      tekkb wrote:

      There are issues with this due to the plexpass version as well. We do not want to cause any rifts with the plex group.
      I understand that part I'm currently a subscriber to plex and have been since 2013.

      Just thinking that with a lot of the threads I see it's people who don't know how to use things like ssh even if I find it quite easy to now. I remember when I first started it was very difficult to find the motivation into doing it when it was so confusing.


      The meaning I'm trying to get across is that for me this far seems easier than having to put in the package every plex update as well as an easy way to say this is what package we think is best. If you want to update there you go but we don't support it yet and it may break or something and also a little note asking for bugs if a new version errors due to some major update.
      I also don't mind looking into making it while you guys get the rest of the plugins up to date.

      Unless I've got the completely wrong idea of how you do it? Also plex doesn't make it easy getting the latest versions. :D
    • Nope, not two weeks. Usually just tekk's approval or a few forum users. Too many people want the latest version so I don't wait two weeks.

      sonarr doesn't use apt/dpkg packages to install. That is why it has an update button/combobox. While plex probably has a package like that, it needs to be modified by a human to work with Debian (and OMV). So, that won't work for plex.
      omv 4.1.15 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      Nope, not two weeks. Usually just tekk's approval or a few forum users. Too many people want the latest version so I don't wait two weeks.

      sonarr doesn't use apt/dpkg packages to install. That is why it has an update button/combobox. While plex probably has a package like that, it needs to be modified by a human to work with Debian (and OMV). So, that won't work for plex.
      Ah bugger.

      Was trying to make it easier on you guys.
    • I believe Sonarr is a Windows program and uses mono like Emby. So it is quite different. The plexpass is the hardest thing to deal with. Also, it is a good idea to wait til the new version is tested. We've seen problems with Plex upgrades and it would really suck if every user's plex was down if we put out an upgrade too soon. The mono Windows based programs are usually pretty easy to rollback, which is weird. I flip versions forwards and backwards on the emby program a lot doing testing.

      The post was edited 1 time, last by tekkb ().