Automation Scripts

Deploy server actions based on existing templates

Aside from the ability to add packages to your environment and configuring them to suit your needs, there will be times when additional actions are required for specific goals. To address this need, we developed the Automation Scripts feature.

As the name implies, this consists of various templates for performing either specific actions like adding a Nginx virtual host, or general actions like executing a bash script or adding a cron entry. You can add multiple configs to be executed on a single deployment.

The deployment of one or more automation scripts does not require the deployment of packages although both can be done at the same time. If packages are included in the deployment phase, the provisioning configs will be executed first.

The templates for the automation scripts are structured in multiple sections depending on the nature of the config, as shown in the table below:

Template Type

Description

cron

Schedule the execution of certain scripts, start/stop services and other actions on the target server.

directory

Offers "Directory path", "Directory permissions", "Directory owner" and "Directory group" and facilitates the creation of a directory in the desired path.

exec

Offers an array of specific action templates like: "linux_install_composer", "linux_install_redis_tools", "Install docker _ docker compose", etc. Each of them can be edited in the script editor as well as modifying the working directory or the user under which they are executed.

file

Offers templates to add NGINX virtual host and config as well as a template for a general system file.

link

Offers the "Link path" and "Link source directory". Enables the creation of a link to a specific file of directory.

package

Specify system packages to install upon the next deploy.

service

Lets the user control a specific system service.

There are some common fields for each template ("Enable plugin", "Action title", "User", "Description" and "Script Editor") as well as some specific ones depending on the type of script. The fields are described in detail for each resource group, in each one's respective doc page.

Find out how to add an Automation Script by goin to: