CLOUD PAAS / APPLICATION SETTINGS

Change Domain name between ENV

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 Change Domain name between ENV 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.

While the system is in use You can face the need to upgrade or fix your system. And of course before you use it in a production system. You'll need to complete some testing first, and Ruk-Com Cloud can easily do this by swapping domains between development and production systems.

With this function Users in your system will still be able to use it normally. For example, You have successfully imported a new version of the system to the development env and swapped URLs with the production env with a few clicks.

- If you want to use domain name switching, you should not enable Public IP for every node in your env.

- In case it is necessary to use an extranal IP to point to your env (such as in an application server or balancer) after the switch is complete. You'll need to provide the correct CNAME on your Manage Domains page. Otherwise all calls from the user will be routed to the old env.

So let's see how domain switching works.

Creating Env for development

  1. Select the production env.
Ruk-Com Cloud PaaS procedure screenshot
  1. Open the website to see that everything is working properly.
Ruk-Com Cloud PaaS procedure screenshot
  1. Clone the actual env to be used for setting up, editing, and testing the system. Cloning the env. The cloned env will have all the information and settings the same as the original. We will call the env that we cloned as the env for testing. More details on cloning the env can be found in the method.Clone Environment
Ruk-Com Cloud PaaS procedure screenshot
  1. Open the env browser for testing to verify that everything works as expected.
Ruk-Com Cloud PaaS procedure screenshot

Steps to edit the application

  1. Configure or modify the system as desired by deploying via GIT/SVN.
  2. Deployment Guide
  1. After successfully deploying, open the browser to check that the modifications can work normally.
Ruk-Com Cloud PaaS procedure screenshot

Setting up domain for Env

  1. Press the "Settings" button on the env where you want to set the domain. (If you don't have a domain yet, you must order a domain first.)
Ruk-Com Cloud PaaS procedure screenshot
  1. After setting up, wait for DNS to update for a moment, then test entering through the specified domain name.
Ruk-Com Cloud PaaS procedure screenshot

Steps for switching domains

The next step after testing the fix is to switch domains.

  1. Press Settings.in the env that we want to switch (In this example we will switch the production env and the test env)
  2. In the custom domains menu, scroll down the screen to find the Swap Domains section.
  3. Select the env for which you want to switch domains. (In this example, we are switching the domain to use with the env we are using for testing.) Once selected, press the "Swap" button.
Ruk-Com Cloud PaaS procedure screenshot
  1. After pressing the "Swap" button, check the domain name in the Domain binding field. You will find that the domain has been changed to another domain name.
  2. After that, open the browser to test.
Ruk-Com Cloud PaaS procedure screenshot

If you have problems switching domains You can contact our team atRuk-Com customer portal