Application Lifecycle Management

Objective

This guide explains how to use Application Lifecycle Management 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.

How do we manage Application Lifecycle in Ruk-Com Cloud?

Developing a complex system or improving the functioning of the system Including the part that contacts users. that must be revised all the time to accommodate the needs of the user Even if the size of your system is not very large. But you can separate the work system. For use in system development or testing by separating the environment so as not to affect the production that users are using. Creating a system like this requires you to have an understanding of the cycle of system development from the system development stage to actually putting the system into use (development => production).

The Application Lifecycle management of the system with Ruk-Com Cloud can be easily managed with an automated system, whether it is creating, setting up, deploying programs to the system, changing domain names, etc. As an example for managing the Application Lifecycle system, we will make an example of making the environment for system development separate from the environment for real users. We will follow the steps below.

• Creating a simulated environment for users
• Deploying the program into the Environment
• Creating a simulation environment for developers
• Modifying and improving programs in the Developer Environment

Creating a simulated environment for users

1. Login added to the Ruk-Com Cloud management page.
2. Press the "NEW ENVIRONMENT" button to enter the environment creation process.

1. Select the application you want to install. (In the example using PHP) Set the number of cloudlets to use. Or if you want to specify an Environment name, you can edit the "Environment name" field.

1. Press the "Create" button and wait a moment. The environment you created will be displayed in our management page.

Deploying the program into the Environment

1. In this example we will deploy a program using Git.
2. Click on the application you want to deploy and then press the "Deploy from Git / SVN" button.

1. After pressing the button, a page will pop up where you can fill in the Git information you want to use.
2. Select the Git/SVN tab.
3. Select the Repository you want. If you don't have one yet, click on "Add New Repository".

1. After clicking on "Add New Repositoty", fill in the Repository information that we want to deploy.
2. Name the Repository.
3. Select the "Git" tab.
4. Enter the URL of the Git Repository.
5. Select the branch you want to use.
6. Enter Login Git
7. Enter your Password or Token or use it as an SSH Key.

1. After completing the settings in Git, press "Add", after which you will return to the Deploy settings screen.
2. Select the Repository you want to use.
3. Select the branch you want to use based on the Git Repository.
4. Select the path where you want to place the file. Normally, the default value is "ROOT".

Creating a simulation environment for developers

Finally, it's time to create a development env after we've prepared the production env. In order to use the Application including various settings of Env to be consistent with Env Production, we will clone the entire Env.

1. Clone the production env by selecting the env you want to clone and pressing "Clone Environment".

1. After pressing, let us name the env or use the default name. Once you've set your name, press the "Clone" button.

1. When the clone is finished, we will get an env with the name we set and the same settings as the production that we cloned.

Modifying and improving programs in the Developer Environment

After we have the env for development, we will test and modify the program so that it does not affect our production.

1. After we have finished editing in Git, press update to pull the latest data from Git.

1. When the update is complete, test access through a browser.

3. When checking information on the env side of Production

1. Check the env side of develop that we have edited.

From the example above, it is easy to see the application lifecycle by separating the part of system development from the part of the work system that actually has users. Reduce errors for users during system development.