Module for Blesta: a paid order creates a line or a sub-reseller account, and renewal, suspension and cancellation in Blesta are carried out on the panel.
How it was testedEvery module function was run against a panel through a stand-in for Blesta. It has not yet run inside a licensed Blesta.
Install steps
- Upload the components folder of the archive into the root folder of Blesta, so that components/modules/xtreampro/ exists.
- In Blesta open Settings → Company → Modules → Available and install Xtream UI Pro.
- On the panel, sign in as the reseller account the orders are charged to and create its API key.
- Add a panel to the module: the API host name, the port, whether it uses SSL, and the API key.
- Create a package with the module Xtream UI Pro and choose what it sells: a line with its package, or a sub-reseller account with its credits.
Early version: read the notice and test it before using it in production.
SHA-256 3e0e980209dd6f794bfa40ec41887db38518f7e02d6407aee7d3fcf8a17a6b11
Server plugin for ClientExec: activating a package creates a line or a sub-reseller account, and suspension and deletion in ClientExec are carried out on the panel. ClientExec does not tell a server plugin about renewals, so renewing is an action the admin runs.
How it was testedIts core (API client and provisioning rules) was run against a panel; the part that plugs into ClientExec has not run inside ClientExec yet. The README lists what is unverified.
Install steps
- Extract the archive into the root folder of ClientExec, so that plugins/server/xtreampro/ exists.
- On the panel, sign in as the reseller account the orders are charged to and create its API key.
- In ClientExec add a server with the plugin Xtream UI Pro: the API host name, port, whether it uses SSL, and the API key.
- On a product choose that server and set what it sells: a line with its package, or a sub-reseller account with its credits.
Early version: read the notice and test it before using it in production.
SHA-256 665079f289bd639c1456434efefdaa4c537cb0ee009915baf69d13c101da8c25
Service module for FOSSBilling: a paid order creates a line or a sub-reseller account, and renewal, suspension and cancellation in FOSSBilling are carried out on the panel.
How it was testedRun end to end inside FOSSBilling 0.8.8 against a panel.
Install steps
- Extract the archive into the root folder of FOSSBilling, so that modules/Servicextreampro/ exists.
- In the FOSSBilling admin area open Extensions and activate Xtream UI Pro.
- On the panel, sign in as the reseller account the orders are charged to and create its API key.
- Open Extensions → Xtream UI Pro, enter the API address and the API key, save and press Test connection.
- Create a product of the type Xtreampro and choose on its Configuration tab what it sells: a line with its package, or a sub-reseller account with its credits.
Early version: read the notice and test it before using it in production.
SHA-256 05570647acea0df27f95469357bc9515b456ad5889d2c8e21e63586e95deaa82
Command-line script for the Script Provisioning module of HostBill: creating, suspending, unsuspending and terminating an account in HostBill is carried out on the panel. Any system that can run a command on billing events can use it.
How it was testedThe script was run from the command line against a panel. It has not yet run inside a licensed HostBill, which has no renewal event: the README says how to call renew.
Install steps
- Copy the folder xtreampro of the archive to the HostBill server, outside the web root.
- On the panel, sign in as the reseller account the orders are charged to and create its API key.
- Copy config.sample.php to config.php, enter the API address and the API key, and make the file readable by its owner only (chmod 600).
- Put the two-line wrapper from the README into the scripts folder of HostBill and make it executable.
- On a product with the module Script Provisioning, set the script and its arguments for each event as listed in the README.
Early version: read the notice and test it before using it in production.
SHA-256 4b982f82064273be10feb08612dea9bba5d033b3db7feb76dc2e05b715924994
Webhook bridge for Invoice Ninja: a small PHP application you host yourself. Invoice Ninja posts it a webhook when an order is paid or revoked, and the bridge creates, tops up or disables the lines and sub-reseller accounts on the panel and emails the buyer their sign-in details.
How it was testedThe bridge was run against a panel with signed sample webhooks of Invoice Ninja. It has not yet received webhooks from a real Invoice Ninja account; the README lists what is unverified.
Install steps
- Extract the archive on your web server and point an HTTPS site at its public folder only.
- On the panel, sign in as the reseller account the orders are charged to and create its API key.
- Copy config.sample.php to config.php outside the public folder, enter the API address, the API key and the webhook secret, map your products to packages or credits, and make the file readable by its owner only (chmod 600).
- In Invoice Ninja open Settings → Account Management → Webhooks and add webhooks for the invoice events listed in the README, pointing at https://your-bridge/hook/invoiceninja, with the custom header from config.php as the shared secret.
- Run php bin/bridge.php check to test the configuration, and schedule php bin/bridge.php retry every few minutes to repeat what failed.
Early version: read the notice and test it before using it in production.
SHA-256 5ec87762ca1dbd5baa248533bb54ae8d7c8f7673d08d7b1e6dcd66d50d30c855
Server extension for Paymenter: a paid order creates a line or a sub-reseller account, and paid renewals, suspension and termination in Paymenter are carried out on the panel.
How it was testedRun end to end inside Paymenter 1.5.9 against a panel.
Install steps
- Copy the extensions folder of the archive into the root folder of Paymenter, so that extensions/Servers/XtreamPro/ exists.
- On the panel, sign in as the reseller account the orders are charged to and create its API key.
- In the Paymenter admin area open Servers, create a server of the type Xtream UI Pro and enter the API address and the API key.
- Create a product, attach it to that server and choose what it sells: a line with its package, or a sub-reseller account with its credits.
- Keep the queue worker and the cron job of Paymenter running: they create, suspend and terminate the services.
Early version: read the notice and test it before using it in production.
SHA-256 8ec7451a1aba1bff4df74da323289218f5637789b5498d8c97ffd360b37ad1e2
Webhook bridge for Upmind: a small PHP application you host yourself. Upmind posts it a webhook when an order is paid or revoked, and the bridge creates, tops up or disables the lines and sub-reseller accounts on the panel and emails the buyer their sign-in details.
How it was testedThe bridge was run against a panel with signed sample webhooks of Upmind. It has not yet received webhooks from a real Upmind account; the README lists what is unverified.
Install steps
- Extract the archive on your web server and point an HTTPS site at its public folder only.
- On the panel, sign in as the reseller account the orders are charged to and create its API key.
- Copy config.sample.php to config.php outside the public folder, enter the API address, the API key and the webhook secret, map your products to packages or credits, and make the file readable by its owner only (chmod 600).
- In Upmind add a webhook endpoint pointing at https://your-bridge/hook/upmind for the contract product and invoice events listed in the README, and put its secret into config.php.
- Run php bin/bridge.php check to test the configuration, and schedule php bin/bridge.php retry every few minutes to repeat what failed.
Early version: read the notice and test it before using it in production.
SHA-256 5ec87762ca1dbd5baa248533bb54ae8d7c8f7673d08d7b1e6dcd66d50d30c855
Provisioning module for WHMCS: a paid order creates a line or a sub-reseller account, and suspension, unsuspension, termination and renewal in WHMCS are carried out on the panel.
How it was testedEvery module function was run against a panel through a stand-in for WHMCS. It has not yet run inside a licensed WHMCS.
Install steps
- Extract the archive into the root folder of WHMCS, so that modules/servers/xtreampro/ exists.
- On the panel, sign in as the reseller account the orders are charged to and create its API key.
- In WHMCS open System Settings → Servers → Add New Server: choose the module Xtream UI Pro, enter the API address as hostname and the API key as password, then press Test Connection.
- Create a product, select Xtream UI Pro under Module Settings and choose what it sells: a line with its package, or a sub-reseller account with its credits.
- From then on WHMCS creates, suspends, unsuspends, terminates and renews them by itself. Every new line, renewal and sub-reseller account is charged to the credits of the reseller account.
Early version: read the notice and test it before using it in production.
SHA-256 4cff697ee7c4abe6cc32afeea8ff4ba85cb63017982d0d33ac9060e5dfe4f6ae
Product module for WISECP: a paid order creates a line or a sub-reseller account, and renewal, suspension and cancellation in WISECP are carried out on the panel.
How it was testedEvery module function was run against a panel through a stand-in for WISECP. It has not yet run inside a licensed WISECP; the README lists what is unverified.
Install steps
- Upload the archive in WISECP under Modules → Product → All Modules → Upload Module, or extract it into the root folder so that coremio/modules/Product/XtreamPro/ exists.
- On the panel, sign in as the reseller account the orders are charged to and create its API key.
- Open the module Xtream UI Pro, enter the API address and the API key, save and press Test connection.
- Create a product in a special product group, choose the module Xtream UI Pro on its Automation tab and set what it sells: a line with its package, or a sub-reseller account with its credits.
Early version: read the notice and test it before using it in production.
SHA-256 555cf120190a4240032ce70ef4718e27c1b2314d225093e634bf91f24f28f3e2