Cloudmini

Resell Cloudmini VPS and proxy plans from Blesta, with every order placed automatically and live server details in your client's own area.

What it does

Reselling VPS and proxy plans usually means placing every order by hand and then fielding tickets whenever a client needs their server's current IP, credentials or status. This module closes that gap: the moment a service is activated, Blesta places the order with Cloudmini automatically and stores the order, service and IP details on the service record. From there, both your staff and your clients get a live Overview of the server (IP, login credentials, specs, location, status, fetched fresh from Cloudmini rather than a stale copy) and an Actions tab to reboot, start, stop, reinstall or reset the password of the server themselves, with a confirmation step in front of anything disruptive.

Key features

• Automated VPS and Proxy Ordering: The Cloudmini order is placed automatically as soon as a service is activated, and the order, service and IP details come straight back onto the Blesta service, so nothing is keyed in by hand.
• Four Product Types in One Module: Sell Normal VPS, Proxy, Proxy Res Static and fully custom builds from the same module, each with its own package form covering region, plan, ISP or CPU, RAM, disk and operating system.
• Live Server Overview: An Overview tab shows the server as it is right now, status, IP, port, login credentials, CPU, RAM, disk and location, fetched live from Cloudmini instead of a stale stored copy.
• Self-Service Server Actions: Clients reboot, start, stop, reinstall or reset the password of their own server from an Actions tab, with a confirmation step in front of anything disruptive, and the resulting new IP or password is shown as soon as the action completes.
• Sell Every Tier From One Package: Attach Blesta configurable options named for the package's own settings (region, plan, ISP, CPU, RAM, disk, OS) and clients pick their own sizing or extras at checkout, each value checked against what Cloudmini actually offers before the order is placed.
• Ready-Made Welcome Email: A welcome email template ships with the extension and loads onto any new package in one click, already filled with the service IP, type and order/service IDs.
• Try It Without Credentials: A built-in Mock API Mode serves bundled sample responses so you can build packages and place a full order end to end before you have a Cloudmini account.

Installing Cloudmini

Before you start

• If you are on the leased (subscription) licence, the Blesta Club Subscription Manager must be installed and your subscription active. The owned and owned-source licences have no such requirement.
• You will need a Cloudmini account and an API Token to provision real servers. If you just want to try the module out first, you don't need either: a built-in Mock API Mode runs the whole module from bundled sample data.

1. Upload the files

Upload the extension folder into your Blesta installation so it lands under your Blesta directory at:

components/modules/cloudmini/

For example, on a typical install: /var/www/html/blesta/components/modules/cloudmini/

2. Install it in Blesta

1. Log in to your Blesta admin area with a staff account that has the Modules permission (or, at minimum, Install Module and Manage Module) under Settings in Manage Staff Groups.
2. Go to Settings > Company > Modules and click the Available tab.
3. Find Cloudmini in the list and click Install.

3. Configure it

1. Go to Settings > Company > Modules, open the Installed tab, and click Manage next to Cloudmini.
2. Click Add Server and give it a Server Label (any name you'll recognize it by) and your Cloudmini API Token. The token is checked against the Cloudmini API when you save, so an invalid one is rejected right away.
3. To try the module without a Cloudmini account, tick Mock API Mode on the server instead. A mock server needs no token and serves bundled sample responses; it provisions nothing and is for demos and testing only.

You're ready to go - see the usage guide for a walkthrough of day-to-day use.

Updating Cloudmini

Upgrading works just like installing: upload the new files over the old ones, then run the upgrade from the same page you installed it on.

1. Back up your current extension files first - good practice before any upgrade.
2. Upload the new version over the existing folder, replacing the old files.
3. Log in to your Blesta admin area and go to Settings > Company > Modules.
4. Find Cloudmini and click Update to run the upgrade.

Version-specific notes

• v2.0.0: This is a feature release. You can now add Blesta configurable options named region, plan, isp, cpu, ram, disk or os to a package so clients can pick their own sizing at checkout; use Select or Quantity options, never Text. Staff and clients both gain an Overview tab showing live server or proxy details, and the Actions tab now asks for confirmation before running anything disruptive (Reboot, Stop, Reset Password, Reinstall, Change IP), showing the refreshed details once the action completes. New packages are pre-filled with a built-in welcome email template. This version also fixes an incomplete package placing an incomplete order instead of being refused, the server and proxy passwords being written to the module log in plain text, and the service info panel missing its Status column (and Location, for proxy services). No manual migration steps are required.
• v1.1.0: Each server now has a Server Label, which is what the module page lists instead of the API Token; running the upgrade labels existing servers automatically ("Cloudmini Server 1", and so on), so rename them to something meaningful under Settings > Company > Modules > Cloudmini > Manage if you'd like. The API Token is now stored encrypted; existing rows keep their token in plain text until the row is saved again, so open each server, re-enter its API Token, and save it once. The edit form leaves the token blank on purpose - leaving it blank keeps the stored token unchanged. Each server also gained a Mock API Mode checkbox; leave it off for live servers and tick it only on a demo or test row.

This upgrade is drop-in beyond the notes above - no other steps are needed.

Using Cloudmini

For your staff

Managing servers

Go to Settings > Company > Modules, open the Installed tab, and click Manage next to Cloudmini. This lists your Servers, each one a Cloudmini API credential, with a Mock API column showing whether it serves live data or bundled sample data. Click Add Server to add another, or Edit / Delete next to an existing one. A server's fields are its Server Label, API Token (write-only: the field is always blank when editing, so leaving it blank keeps the stored token unchanged) and Mock API Mode. A server row cannot be saved live (Mock API Mode unticked) without an API Token.

A service ordered against a mock server keeps serving its sample details even if you untick Mock API Mode on the server later, since its order and service IDs belong to no real Cloudmini account. Delete those services before taking the server live.

Building a package

Create a package and assign it to the Cloudmini module. On the package's module fields, choose a Type: Normal, Proxy, Proxy Res Static or Custom. Each type shows only the fields Cloudmini needs for it:

• Normal: Region and Plan, both loaded from Cloudmini.
• Proxy: Region only.
• Proxy Res Static: Region, then an ISP dropdown scoped to the region you picked.
• Custom: Region, then CPU, RAM, Disk and OS, all loaded with the bounds Cloudmini allows for that region once you pick it.

To sell several sizes or regions from one package, add Blesta configurable options named exactly region, plan, isp, cpu, ram, disk or os. A client's selection overrides the package's own value at order time, and is checked against what Cloudmini actually offers before the order is placed, so a package can no longer be oversized for free. Use a Select option (or Quantity for cpu, ram and disk), never a Text option: with Text the client types the value, and only a priced Select or Quantity option charges for what they picked.

A package saved without everything its type needs (for example a Normal package with no Plan) is refused at order time with a message naming the missing setting, rather than placing an incomplete order.

Placing and managing an order

Ordering the service places the Cloudmini order automatically; the order ID, service ID and IP that come back are stored on the service and shown wherever the service is managed. On a service's manage page, under Basic Options > Upgrade/Downgrade, staff can also see and edit the raw Order ID, Service ID, Service IP and Type fields directly, for the rare case a value needs correcting by hand.

You can also see a service's live details at a glance without opening it, by expanding its row on the client's Services list.

The Overview tab

On a service's manage page, the Overview tab shows the server or proxy as it is right now: IP, port, username and password, location and status, fetched live from Cloudmini rather than a stored copy - plus CPU, RAM and disk for Normal and Custom services, or the proxy's HTTPS and SOCKS ports for Proxy and Proxy Res Static services. The stored Service IP is refreshed automatically whenever this tab (or the client's matching tab) is viewed, so an address changed upstream never leaves your records out of date.

The Actions tab

The Actions tab runs a command against the server: Reboot, Start, Stop, Reset Password, Reinstall or Change IP. Pick one from the dropdown and click Execute. Anything disruptive (everything except Start) asks for confirmation first, so a click can no longer run an irreversible action by accident. Once it completes, a success message appears and the tab's details refresh immediately, so a new IP (after Change IP) or a new password (after Reset Password) is visible right away. Change IP is staff-only and is not offered on the client's Actions tab.

Email tags

• module: name
• package: type, region, plan, isp, cpu, ram, disk, os
• service: order_id, service_id, service_ip, type

A package tag renders only for the product types that use it: {package.plan} for Normal packages, {package.isp} for Proxy Res Static, and {package.cpu} / {package.ram} / {package.disk} / {package.os} for Custom. {package.type} and {package.region} are set on every package. A new package is pre-filled with a built-in welcome email using these tags; copy it into an existing package if you'd like to use it there too.

For your clients

Viewing the server

From their service page, clients get the same Overview tab your staff sees: live IP, login credentials, specs, location and status for their server or proxy. The same details are also available at a glance by expanding the service on their Services list, without opening it.

Running actions

Clients get an Actions tab too, offering Reboot, Start, Stop, Reset Password and Reinstall (not Change IP, which is staff-only). Anything disruptive asks them to confirm before it runs, and the refreshed details (a new IP or password) appear as soon as it completes.

Good to know

• Mock services stay demo services. A service ordered while its server had Mock API Mode ticked keeps serving the built-in sample details for good, even after the server goes live, because its IDs belong to no real Cloudmini account.
• The Service IP refreshes on view, not on a schedule. Opening the Overview tab (staff or client) is what triggers the refresh from Cloudmini; there is no background sync.
• Canceling a service in Blesta does not cancel it with Cloudmini. The Cloudmini API has no order-lifecycle endpoints, so suspending, unsuspending, renewing or canceling a service in Blesta only changes its status in Blesta - the upstream order needs handling with Cloudmini directly.