

User places an order for a Plex appbox on your WHMCS installation.An example of a workflow with Kronos would be the following Kronos manages the technical and economical parts of providing Appboxes to users, where these users can then utilize the application. Provide you an almost completely automated and relaxed experience.Īppbox is a term for an isolated shared hosting space in which an application is hosted for a user, for example, a docker container hosting an installation of the Plex Media Server.Automate management of appboxes, invites, user, and billing.Provision and host appboxes running Plex.
Plex appbox full#
Kronosapp is a full system closely tied in with WHMCS that will allow you to: Kronos is shipped with a TMDB and Trakt default API key that you may use, though we strongly advise the use of personal keys.¶ What is Kronos, and what can it do for you? WHMCS (Requires SSH access to whmcs host).Automated deployments when accepting orders.Request lounge (Similar to Ombi, for users requesting media).Node monitoring (keeping nodes alive in case they crash or go down) Requires hosting at Hetzner or a host with an accessible API as well as an Uptime Robot account.In order to utilize optional modules of Kronos, which are listed as follows: Authy API key for secure admin logins (Optional, but highly recommended).SSH key authentication configured on said nodes.Nodes for appboxes to be deployed to(Ubuntu 16.04+).Kronos consists of several modules, some of which have additional requirements. The support system supports "Supporters" allowing you to have moderators that can do limited actions with tickets and appboxes providing a smooth and robust support system to further enhance the user experience ¶ Core requirements for using Kronos On top of providing management of dedicated servers, Docker containers, and providing front-end control to the user, Kronos also features a full support system via tickets, allowing users to submit tickets if they need support. Kronos will allow you smooth and easy management of thousands of Docker containers running Plex or Emby, across a multitude of dedicated servers, while also providing your users a front-end dashboard to manage their docker container, reducing the labor required by making your users self-sufficient in the majority of instances. If users stop paying their bills or cancels, the Kronos backend will also react to this by suspending and deleting appboxes automatically! ¶ In short Products defined in your WHMCS installation are fetched automatically and added to Kronos, allowing you to define rulesets based on them - For example, you may Provision a Plex Appbox product that only allows for 2 transcode slots to reduce resource costs, when configured within Kronos, any accepted order for this product will result in an appbox deployment that is limited to 2 transcodes. The user now has a personal installation of Plex that the user can manage directly via the Kronos front-end (Also known as the appbox dashboard).An appbox is automatically installed for the user on the Kronos backend(must have ssh access to whmcs install), details for accessing the appbox control panel is emailed to the user.¶ What is Kronos, and what can it do for you?
