Instructions can be found on the WebTools GitHub wiki. bundle files to the plugins folder, unfortunately leaving out that shiny new Nvidia Shield again. WebTools can be installed on any system that a person can add. It can handle keeping all of your bundles up to date and provides an easy way to install extra plugins, through its list or the ability to enter a github link. What really makes the UAS (Unsupported AppStore) shine is the ease at installing extra bundles to extend the use of your Plex Media Server. Tip: There is an awesome user manual for configuring WebTools that starts after you get it installed, available here.In the coming weeks, there will likely be tools featured here, on Tool Tuesday, that will be available to install from there. It has now been rolled in with WebTools as UAS2, since the old one sadly stopped working. The Unsupported AppStore has previously been one of the most famous and utilized plugins in the plex ecosystem. This plugin is not limited to the usual channel interface, instead it utilizes a built in webserver to display a responsive web interface that also works from mobile devices allowing you to manage your Plex Server from any device. WebTools 2.0 is a collection of utilities to help with the management of your Plex Server. Quoting the forum thread here, which I have shamelessly plagerized for this post, Manual instructions | WTInstaller instructions (Manual) Windows, OSX, Linux, Unix and Docker | (WTInstaller) Asustor, QNAP, Synology and Windows WebTools is a collection of utilities to help with the management of your Plex Server Write-up by /u/dane22 (Developer), (Developer) and /u/electro_nick_s ( /r/PleX Moderator). If you need help with this or any other tangibly related tool, pop it in the comments! WebTools Please go to the relevant subreddits and support forums, for example:Įach week, we take a look at a tool that may sit on a Plex server stack, but may not be directly Build help and build shares posts go in their respective megathreads No referral / affiliate links, personal voting / campaigning / funding, or selling posts Welcome to /r/Plex, a subreddit dedicated to Plex, the media server/client solution for enjoying your media! Plex Community Discord Rules Should we thus leave it in a _disabled_ state (greyed out) or simply hide it? I would tend to lean on the former, as it would provide further indication to the user that the Rock-on does have a webUI and that changes to the ports were made.Latest Regular Threads: No Stupid Q&A: Tool Tuesday: Build Help: Share Your Build: Submit Troubleshooting Post Files not showing up correctly? If the webUI port (if applicable) is unpublished, the webUI button displayed in the Rock-ons summary page would not work anymore. Should we offer the possibility to edit the container port as well (or leave this for a future and separate issue/PR)?ģ. let user choose to not expose the port (if desired) via checkbox (such checkbox would be checked by default)Ģ. If one chooses to unpublish a port, I can see three possibilities: In the future, we may work on adding the possibility to create the network from here, as an enhancement.ġ. On the next step (or below this one), one may attach the Rock-on's container(s) to one or more pre-existing docker networks. This could be implemented on the Rock-on customization dialog next to the other customization options currently existing (see below).Ĭlicking on the "Ports" button would lead to a dialog to edit all ports: > I would actually like to see an option to export or not the ports in the GUI, _then_ we would have a use for network creation and joining.Īs a result, we can offer an advanced post-install customization option to advanced users to un-publish predefined ports and then join docker networks of interest. Indeed, as described by in the issue referenced above (), joining a docker network would be useful/required only if predefined ports are not published: In order to make custom docker networks (described in #2009) useful, we need to create an interface to edit the ports described in a Rock-on JSON file. It is meant as tracking and discussion material for a work currently **in progress**. This issue relates to step 3 of Rock-ons networking work described in #1982, and … follows steps 1 (#2003) and 2 (#2009).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |