Auto-Deploy Overview

Objective

This guide explains how to use Auto-Deploy Overview 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.

To increase productivity as a developer, Ruk-Com Cloud provides automatic deployment setup that occurs automatically over the course of a project. As such, continuous integration with the relevant application server should be ensured. Re-deployment occurs based on changes applied to the appropriate remote repository. So you can easily work through Git/SVN services.

Just update your code and commit. All changes in the VCS project will be automatically pushed to the production environment after a specified period of time, and unlike Git hooks, the auto-deploy feature does not require any additional configuration.
As for the Git repository and working with SVN, see the steps below.

Project preparation

1. Start with preparationRuk-Com Cloud EnvironmentTo add desired projects with code from Git/SVN

More:
-For Java environments it is necessary to add marven node. For building and pushing code to the appropriate application server.

-Other languages are managed by their own associated compute nodes.

We will use the Maven build node for Java as an example, however other application servers can be configured as well.

2. Once your environment has been created, click the button.Add Projectnext to the appropriate node (e.g.Marvenfor Java or application servers for other languages)

3. In the window that opens Switch to the VCS used tab and fill in the required fields: InsertURLGo to the required repository, specify the authentication details and set a name forcontextwhere the application will be placed

Additionally, in the case of using a Maven build node, you must specify additional names for the project and environment that you want to deploy.

Tips:If you want more details about these options, Please read the relevant instructions from the list below according to the application you are using.

-Maven for Deploy via Git/SVN

-Deploy PHP Projects via Git/SVN

-Deploy Ruby Project via Git/SVN

-Deploy Python Projects via Git/SVN

-Deploy Node.js Project via Git/SVN

Setting up automatic project updates

Now that you have provided all the important information for the deployment, you may proceed to configure automatic updates to your project.

1. Place a check mark on the lineCheck and auto-deploy updatesto enable and expand the relevant sections

OptionsCheckCheck every (minutes) is shown to determine how often the store is checked for new commits that have been pushed since the last check.

You can easily predict from the option name that it will be specified in minutes. For example, if you set the interval 1 minute, the check will be done every minute, and if you specify the interval 1440 minutes, the check will be done once a day.

More:
-If the verification interval is less than the time needed to build or deploy the project, further tasks will wait in the queue until these operations are completed.

-In the case that the application server layer has many nodes, please consider.DetailsAbout the update order

2. Results of these configurations (This, despite a long description, takes less than a minute to identify.) If any changes are made to the application source, those changes will be created and deployed automatically (for Java projects) or simply using project updates. (for remaining languages) once for the specified period of time

ClickAddto confirm

Tips:This frame also includes additional settings which may be useful for management. Proper compatibility of the system with your remote storage


- OptionsCheckout now(presented for non-Java languages) to indicate whether you want to deploy your project immediately after adding or defer this action. (for manual startup later or automatically during the first additional payment with the auto deploy feature enabled)


- OptionsAuto resolve conflictIt is still enabled by default and is similar to the git reset –hard command to prevent merge conflicts during future project updates. This can happen if the same file is edited in both the remote storage and your project. If Ruk-Com Cloud encounters such a problem, conflicting files will be updated according to the stored version. (This is considered a valid file.) It discards any changes made locally. We recommend that you do not disable this option unless you know what you are doing.


- OptionsEnable zero-downtime deployment(Currently available for PHP only) Allows to deploy continuous application updates in ROOT context without interruption of application operation. If this case is enabled, your choice will be remembered and used during all subsequent automatic updates.

Tracking Auto-Updates

To monitor the automatic deploy processing and results, you can view the log files.logappropriate (namevcs_update) for app server or Maven node

Note:You can also reconfigure your deployment through the Git/SVN app settings by going to your environment and selecting the button.EditNext to the appropriate project you will see an open frame similar to the one used for adding projects where you can change the state for any of the options described above. (Just click onApplyto confirm the new settings)

That's all! Just make these simple configurations while adding projects to Ruk-Com Cloud, and feel free to continue working on your code through the Git/SVN repository without having to come back to the dashboard again. You can rest assured that everything will be automatically up-to-date in your production.