Deployment Guide

Deployment Guide

The platform provides several application deployment methods so that users can choose the workflow that best matches their source package, repository structure and application stack.

Dashboard

Deploy an application archive from a local computer or a publicly accessible URL.

Version Control

Deploy directly from a Git or SVN repository and optionally enable automatic updates.

Container Registry

Create a custom application container from an image stored in a public or private registry.

Application deployment options
Available methods for application deployment.
In this article

This guide focuses on archive and repository-based deployment. Registry-based container deployment is managed through the custom container workflow.

Start a Deployment

A deployment can be started from the Deployment Manager or directly from the application server shown in the environment topology.

1

Open the deployment controls

Expand the required environment and hover over the Deployments item under the target application server.

2

Select the deployment source

Choose Local File, URL or Git / SVN according to the application source.

Application server deployment buttons
Start deployment from the application server’s Deployments section.
i

Technology-specific deployment

Java repository deployments typically use a Maven build node. Deployment to Windows-based IIS or .NET environments follows a different stack-specific workflow.

Archive Deployment Configuration

Archive deployment requires an application package and a target environment. Additional settings can be used to control the deployment context, scripts and deployment strategy.

Local File or URLSelect an archive stored on the local computer or provide a direct URL to the archive. When launching from Deployment Manager, the selected package may be filled automatically.
EnvironmentSelect the target environment that contains a compatible application server. When deployment is started from a server, the environment is normally selected automatically.
PathDefine the application context or deployment path. Available options depend on the selected programming language and server type.
HooksRun custom scripts before or after deployment to perform additional configuration or automation.
Deployment StrategyFor a horizontally scaled layer, choose simultaneous deployment for speed or sequential deployment with a delay to reduce downtime.
Zero-Downtime DeploymentFor supported PHP application servers, enable the option to deploy a new application version while minimizing service interruption.
Archive deployment configuration
Configure the archive source, target environment, path and deployment strategy.
1

Select the application archive

Upload a supported archive or enter its direct URL.

2

Choose the target

Select the environment and application server where the package should be deployed.

3

Review optional settings

Configure the path, hooks, deployment strategy and zero-downtime option when required.

4

Start deployment

Click Deploy and monitor the operation in the dashboard Tasks panel.

Git and SVN Deployment Configuration

Repository deployment connects a saved Git or SVN project to a compatible application server. The repository and target environment are the main required settings, while other options control builds, updates and conflict handling.

RepositorySelect a Git or SVN project saved in Deployment Manager or open the repository form to add a new project.
BranchSelect the repository branch to deploy. The default branch is used when no alternative is specified.
EnvironmentSelect the environment containing the target application server.
PathDefine the deployment context when supported by the selected application stack.
BuildFor Java applications, choose an existing Maven build node or add one to the environment. A repository working directory can also be specified.
HooksApply scripts before or after the deployment process.
Deployment StrategyFor a scaled server layer, select simultaneous deployment or sequential deployment with a configurable delay between nodes.
Check and Auto-Deploy UpdatesPeriodically check the repository for code changes and deploy the latest revision automatically.
Auto-Resolve ConflictsReplace conflicting local files with the repository version. Local changes in affected files are discarded.
Zero-Downtime DeploymentFor supported PHP servers, deploy application updates while minimizing service interruption.
Git and SVN deployment configuration
Configure the repository, branch, target environment and deployment behaviour.
1

Select or add a repository

Choose the saved Git or SVN project from Deployment Manager or add the repository details.

2

Select the branch and environment

Choose the source branch and the target application server environment.

3

Configure deployment behaviour

Review the application path, build node, hooks, deployment strategy, automatic updates and conflict resolution.

4

Deploy the project

Click Deploy to fetch the repository content and deploy it to the application server.

✓

Sequential deployment

For applications that must remain available during an update, deploy to scaled instances one at a time and set a suitable delay between server operations.

Manage a Deployed Repository Project

After deployment, the repository settings can be updated from the application server’s Deployments section.

1

Locate the deployed project

Expand the environment and application server, then find the required repository project under Deployments.

2

Open project settings

Click the Edit action for the deployed project.

3

Apply the required changes

Update the repository branch, deployment path, automatic update interval, hooks or other available settings, then save the configuration.

Edit deployed repository project
Open the Edit action to update an existing Git or SVN deployment.

Expected Result

After the deployment completes successfully, the application can be opened from the dashboard using the Open in Browser action. Application behaviour can be reviewed through server logs, managed through the configuration file manager or maintained through SSH access.

Important Notes

  • Use a deployment package and application server type that are compatible with the selected programming language.
  • For Java repository deployment, verify that a Maven build node is available and correctly configured.
  • Sequential deployment is recommended when application availability must be maintained across scaled servers.
  • Automatic conflict resolution can overwrite local changes made directly on the server.
  • Review the Tasks panel and server logs when a deployment fails.
  • Confirm that repository credentials and branch permissions are valid before enabling automatic deployment.

Related guides