Deployment Guide
This guide has been reviewed and reformatted for Ruk-Com Cloud PaaS. Screens may vary slightly by platform version.
Click or tap a screenshot to view it at its original size.
Objective
This guide explains how to use Deployment Guide on Ruk-Com Cloud PaaS, with ordered procedures and practical verification points.
Before you begin
- Sign in with an account permitted to manage the relevant environment.
- Confirm the target environment, region and resources before saving changes.
- Create a backup or rollback plan before changing a production system.
Ruk-Com Cloud PaaS supports multiple application automation deployment methods, allowing you to choose the most appropriate option to suit your specific needs:
- wp:list-item
- Dashboard- Thedeploy via archive(Specify as a local file or URL) /wp:list-item wp:list-item
- VCS- allowdeploy from VCS repositoryyours (e.g. Git, SVN, Bitbucket) /wp:list-item wp:list-item
- Hub Registry- Create custom containers with your application based on the Docker image stored inpublicorprivateregistry /wp:list-item wp:list-item
- Plugins- deploys the project using one of the most popular software development tools (Ant Task,Eclipse,Intellij IDEA,MavenorNetBeans) to integrate with the platform /wp:list-item

For more information about the last two options, see the appropriate links. In this guide we will explain deploying via archives and VCS repositories can be called from.Deployment ManagerOr hover over Deployments and select your desired options.

The first two icons are (Local file and URL) corresponding to deploy via Archive and the last icon is (Git/SVN) - to deploy from the VCS repository.
Select the appropriate options and click to proceed with configuring your deploy.
Note:
- VCS type deployment for Java application servers is done usingMaven build nodePlease see the manual link for more details.
-Performing.NET deploymentFor Windows-based IIS server applications, this differs from the standard flow described in this guide.
Archive Deployment Configurations
This is very simple and can be done in seconds by setting two key parameters (such as providing the necessary archives and specifying the target environment). The deployment can be tailored to your specific needs by making additional configuration changes.
The sections below describe in detail the options within the frame:
- wp:list-item
- Local file(orURL) - points to the archive to deploy (will be automatically selected when installing from Deployment Manager)
- Environment- Select the target environment with the application server. (It will be selected automatically when installing from the application server.)
- Path- Set up a custom environment according to your needs. This option may be limited by the specific programming language used (e.g.PythonandNode.jsThere is a single predefined path for deployment)
- Hooks- usescriptsthat are provided before/after the deploy process
- Deploy Strategy(for deployscalable server) - allows choosing between a relatively faster concurrent deploy option that causes short downtime, and a sequential deploy option with a delay to perform the deployment on each server one at a time with a delay set between operations that ensures the application runs.
- Enable zero-downtime deployment(For PHP server only) - Modify (if this option is selected) the deploy flow toAvoid application crashes downtime /wp:list-item

Git / SVN Deployment Configurations
This is very simple and can be done in just a few seconds by setting two main parameters (for example, selecting the desired storage location).repositoryfrom the Deployment Manager and specify the target environment). The deployment can be tailored to your specific needs by modifying the additional configuration.
The sections below describe in detail the options within the frame:
- wp:list-item
- Repository- Allows selecting Git/SVN project from Deployment Manager (or jump to additional form)
- Branch- Set the branch used for storage (master by default)
- Environment- Select the environment with the application server. (It will be selected automatically when installing from the application server.)
- Path- Set up a custom environment according to your needs. This option may be limited by the specific programming language used (e.g.PythonandNode.jsThere is a single predefined path for deployment)
- Build- (for deploying Java application) allows selectionMaven build node(or add a node to one of the target environments) and, if necessary, select the Working Directory storage location.
- Hooks- usescriptsthat are provided before/after the deploy process
- Deploy Strategy(for deployscalable server) - allows choosing between a relatively faster concurrent deploy option that causes short downtime, and a sequential deploy option with a delay to perform the deployment on each server one at a time with a delay set between operations that ensures the application runs.
- Check and auto-deploy updates- Enable periodic checking for code changes in your repository. (with configurable frequency) If available, the project will automatically start deploying.
- Auto-resolve conflicts- Prevent conflicts in combinations By updating conflicting files to the repository version (i.e. changes made locally will be discarded).
- Enable zero-downtime deployment(For PHP server only) - Modify (if this option is selected) the deploy flow toAvoid application crashes downtime /wp:list-item

within minutes Your application will be successfully deployed. You can now access it by clicking on the button.Open BrowserAnalyze through Logs or manage with file manager via SSH access.
Editing Git / SVN Projects
You can modify your deployed VCS project with the click of a button.Editfor proper deployment

Within the open frame you can edit the same parameters as described above for the deploy frame, for example changing branches, adding hooks, enabling auto-deploy updates, and so on.

Note:If the project's storage access credentials are changed You must provide new information to continue working on this project. First fix the authentication for the storage atDeployment Manager
You then need to edit all existing projects from the repository where a frame will pop up to confirm whether you want to update the credentials or not.
Click the buttonYesto use new information for a project