![]() ![]() After waiting a day or two, the update propagated to FreshPorts. Apparently it checks for updates periodically and notifies me when one is available. The first notification was from my home Plex media server. ![]() I didn’t know how upgrades would work until I needed to perform one, so it’s just a waiting game for a new version of Plex to be released and see how things propagate. I was then able to enjoy my home Plex media server for a few weeks. Copy-pasting the commands worked as advertised and everything was fairly painless. The install process also ended with a few paragraphs of instructions on how to configure Plex to automatically start every time that instance of FreeBSD (in my case, the FreeBSD Jail) boots up. Plus, if this goes well, it would be a one-time cost.Īfter the FreeBSD jail was set up, I opened a shell window into it and typed pkg install plexmediaserver which thankfully took care of downloading and installing all the binaries. I had to manually create the FreeBSD Jail running on my FreeNAS box, which was harder than the built-in plug-in version but was not horrible. When I found out Plex media server is also offered as part of the FreeBSD Ports and Packages Collection (tracked via “ FreshPorts“) I hoped that might be a much better way to go. In order to update, Google found manual instructions that were… well, let’s just call them ‘nontrivial’. (Either it is hard to find, or that it doesn’t exist, it’s not user-friendly either way.) The version of Plex media server I received using the default plug-in installation process was several versions out of date and it looked like I was pretty stuck. One problem I had with the FreeNAS plug-in architecture is the lack of a user-friendly update system. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |