It automates the deployment process, so containers are created, configured, and assigned to clients instantly upon purchase.
Clients can control their containers directly from the WHMCS client area, including start, stop, restart actions, viewing logs, accessing the console, and more.
You can also enable "App Templates" to let clients reinstall their stack using predefined configurations.

We will guide you step by step through the whole installation and configuration process.

The content of the package to upload should look like this.

The file is located in 'modules/addons/PortainerDockerContainers/license_RENAME.php'. Rename it from 'license_RENAME.php' to 'license.php'.

Enter your license key between quotation marks as presented on the following screen. You can find your license key in our client area → 'My Products'.

This folder is available at '/yourWHMCS/modules/addons/PortainerDockerContainers/'.

Log in to your WHMCS admin area. Go to 'System Settings' → 'Addon Modules'. Afterwards, find 'Portainer Docker Containers' and press the 'Activate' button.

To do so, click on the 'Configure' button, tick 'Full Administrator' and press 'Save Changes'.

You can access your module under 'Addons' → 'Portainer Docker Containers'.
Read the guide provided on the 'Dashboard' or continue with this documentation.

In the Server Details section:

• Set Module to 'Portainer Docker Containers'
• Enter your Portainer API key in the Password field (use an admin account token).
• Click Test Connection to ensure proper communication with the Portainer instance.
• Click the Configure button to select your desired environment (Portainer endpoint).
  Note: The environment defines all core settings, such as available resources (CPU, RAM, GPU) and what container or stack templates will be used.
  These are configured directly in Portainer. In the WHMCS module, you only choose from existing environments.
• After selecting the environment, the Access Hash will be filled in automatically.
• If your Portainer server uses SSL, ensure the Secure' checkbox is enabled.
  You can also enable the Override with Custom Port option and enter your custom Portainer API port.
• Finally, adjust SSO Access Control if needed, then click Save Changes.

Click on 'Create a New Group' .

To create a product click on 'Create a New Product' .

'Product Type' should be set to 'Shared Hosting'.

The module should automatically save and reload settings. If not, click on 'Save Changes' manually.

• Default Instance Name – Enter the default name to be used when creating a new stack or container. The name must contain only lowercase letters, digits, hyphens (-), or underscores (_).
  Available variables: {$domain}, {$client.id}, {$service.id}, {$order.id}, {$random}.
  If left empty, the domain name will be used.

• Default Username – Enter the default username to be used when creating a new user.
  Available variables: {$domain}, {$client.id}, {$service.id}, {$order.id}, {$random}.
  If left empty, the domain name will be used.

• Open Container Console in New Window – Enable this option to open the container console in a new window when the feature is available in the client area.

App Templates Configuration - To create instances based on stack or container applications, you must first configure the App Templates in the module's addon.
Once your applications and groups are set up there, you can select the desired application in the product's Module Settings tab to be used during instance creation.
Please refer to the App Templates section of the documentation for detailed setup instructions.

• Default Application Group - group of applications allowed for reinstalls, see the groups section.
• Default Application - default application to be installed on the VPS, see the applications section.

• Memory Reservation [MB] - Specify the amount of memory (in MB) reserved for the container. Set to 0 for no reservation.
• Memory Limit [MB] - Set the maximum amount of memory (in MB) the container can use. Use 0 for unlimited.
• CPU Limit [Cores] - Set the maximum number of CPU cores available to the container. Use 0 for unlimited.
  

Alternatively, you can use configurable options to allow clients to define these limits at checkout.

• Container Details – Show basic information about the container, such as status, IP address, and resource usage.
• Stack Details – Display information related to the assigned stack configuration.
• Start – Allow clients to start their container.
• Stop – Allow clients to stop their container.
• Restart – Allow clients to restart their container.
• App Templates – Enable access to predefined application templates for quick reinstall.
• Environment Variables – Allow clients to view or manage container environment variables.
• Published Ports – Show mapped ports between the host and the container.
• Container Logs – Provide access to real-time container logs.
• Console – Allow access to the container's interactive console.
• Graph – Show performance graphs such as CPU, memory, and network usage.
• Assigned Containers – Display a list of all containers assigned to the client.
• Action Logs – Provide a history of actions performed on the container (e.g. start, stop, reinstall).

These options define what information and controls admins will see within the WHMCS service management page:

• Service Actions – Perform start, stop, or restart actions directly from the admin area.
• Stack Details – View the full configuration and status of the assigned stack.
• Assigned Containers – Display all containers linked to the service.
• Container Details – Show detailed information about the container, such as IP address, image, and resource usage.
• Published Ports – View the port mappings for the container.
• Environment Variables – View environment variables set for the container.
• Container Logs – Access logs generated by the container.
• Graphs – Display real-time resource usage graphs (CPU, RAM, network, disk I/O).
• Action Logs – Review all actions performed on the container or stack from within WHMCS.

Configurable options allow clients to customize container parameters individually during the order process. If no configurable options are defined, the fixed values set in the product configuration will be used instead.

Available Configurable Options:

• app – Application
• memory_reservation – Memory Reservation
• memory_limit – Memory Limit
• max_cpu_usage – CPU Limit

In this brief guide, we will introduce the module’s capabilities and show you how to make the most of its features.

It allows you to add products to the module, enabling the creation of checks for services associated with those products.
It also features several management tools like the queue, translations tool and module logs.

Prepare templates in the 'Applications' tab and gather them into groups in the 'Groups' tab.
For clients to be able to install templates on their VPS, their product has to include an 'Application Group' and allow 'App Templates' in the client area.

You can change the settings and have the guide collapsed by default. Clicking on the 'Additional Actions' button, select 'Options' and 'Collapse Guide'.

You can also use the mass action buttons to manage multiple templates at once.

Navigate to 'App Templates' → 'Groups' and click on the 'Create' button.

• Name
• Description
• Items to include

Note: Keep in mind that Vultr includes Windows licenses (Core and Standard) in their Plans and charges a monthly fee for them.
Since this will affect the Plan price, we recommend not including Windows with other systems in one product.

Find the 'App Templates Configuration' section and 'Default Application Group' field.
Include a chosen group for the product.

See the examples below to learn about the most important options.

1. Navigate to 'App Templates' → 'Applications' and click on 'Create'.

See the official official Vultr documentation too learn how.
Make sure to include your API Key, the request looks like this:

curl "https://api.vultr.com/v2/applications" \
 -X GET \
 -H "Authorization: Bearer ${VULTR_API_KEY}"

Example result:

{
"applications": [
{
"id": 1,
"name": "LEMP",
"short_name": "lemp",
"deploy_name": "LEMP on CentOS 6 x64",
"type": "one-click",
"vendor": "vultr",
"image_id": ""
}

For example 'LEMP' from:

"name": "LEMP",

Note: If you include a 'name' setting detail (see step 4) with the name from the request as its value, you can safely rename the application to something else here.

In our case it is:

"id": 1,

If an application supports scripts, the responsible setting will always be added automatically.
To include a script, edit the setting by clicking on the 'Edit' button next to it.

• Name - do not change this value, this is the setting identifier.
• Field Type - if the 'Visibility' setting is toggled on, this field decides the type of field, we recommend leaving it as is.
• Default Value - this is where you include your script. If 'Visibility' is toggled on, this will be the default value that clients can modify.
  Note: Use the merge field list on the right for reference.
• Validation - optionally, provide Laravel validation rules like 'required'.
• Visibility - this will allow the client to modify the script before installation.

To upload a new picture, click on the 'Upload Image' button.

To delete all images at once, use the additional action button.

Prepare translations for the original English files with this handy built-in tool. For specific instructions on how to use this tool please refer to its dedicated article, you will find it here.

You can filter the module logs by type with the 'Show' buttons:

• Critical
• Error
• Notice
• All (Total)
  

All information on Logs can be found in the dedicated to logs article, you will find it here: https://www.docs.modulesgarden.com/Logs.

At the top, you will find a condensed setup guide, presenting the same information as this documentation.

The basic client area integration allows them to create and .....

Important: Installations will wipe all existing data from the machine.

Ensure successful completion of the module update by carefully following each step, thereby preventing data loss or any unforeseen issues.
Additionally, you will find a current list of supplementary actions necessary for a smooth update process there.

Opt for the Open Source version of your Server Monitoring For WHMCS module to unlock these benefits.
Simply click on either the Get Source Code or Upgrade To Lifetime button found on the product's page in our client area to complete the one-step upgrade process, with a dedicated discount already applied.

Follow a comprehensive guide covering the transition process, the advantages it brings, and step-by-step instructions on what to do next after the order has been successfully finalized.