Export Environment

Objective

This guide explains how to use Export Environment 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's unlimited cloud platform name proofing allows for easy migration of environments between clouds to find the one that best suits your needs, which consists of two main steps - exporting an existing environment (details on this operation can be found below) and importing it for installation in Ruk-Com Cloud. Both operations take only a few minutes. As a result, you will receive a copy of the same ready-to-use environment running on another Ruk-Com Cloud installation.

Note:so thatEnvironment Export / Importfeature works correctly To initialize the platform (e.g. export environment), you should openport 7979to be used for downloading source files that move the environment during subsequent import operations. Therefore, depending on the provider's configuration, export environments from our partner platforms (specifically Elastx and Everdata) cannot be imported into other Ruk-Com Cloud installations.

How to get a copy of Environment

During export all information about the environment (such as topology settings, application deployment, links to archives with configuration and personal data, etc.) is collected in a single.json file. The compressed JSON package can be downloaded to your computer for storage or deployment on another platform.

So if you want to export a copy of your environment, log in to your Ruk-Com Cloud account and follow the instructions below:

1. Click on the buttonSettingsin the environment where you want to export (For example, moving java-app in our case)

Note:Your Environment should have statusRunningfor export

2. When opening a tabSettingsThen click on the sectionExport

3. WindowEnvironment ExportA window will appear with 3 environment export options:

• Topology Settings- Environment configuration that you set through the topology wizard (this is required and enabled by default)
  
• Private Data- Files in directories of the applications you deploy and personal data stored in your database server.
  
• Configuration Files- All files, accessible through configuration management at your dashboard and GIT/SVN project settings (e.g. storage links, access credentials, attached private SSH keys, etc.)

Note:This ensures that your applications and data are safe. We recommend that you do not delete the original environment you are exporting. Until it is successfully imported to another platform

Environment Export depends on the type of container environment you have, keeping the following points in mind:

• Information from the container usedElastic VPS,Maven,DockerAnd Windows will not be exported, although it will still be included in the topology in which you imported the environment (such as building from scratch), so you can manually reconfigure these servers later.
  
• When exporting an NGINX server (either a load balancer or a node server application type), the appropriate node is paused and automatically restarted to retrieve the dump.
  
• exportPrivate SSH keyAlong with the GIT storage settings, it cannot be removed from the imported environment and does not show up on the dashboard even though it is still used for connections. However, it will be overridden if a new one is selected within the GIT project's settings window.
  

4. When the export is finished. The export time and date will appear in the list.Exported Environment Copiesand can click on the item to download the file.jsonCompiled file and export the environment to your machine or right click to copy the URL directly to the manifest (which can also be used during import).

You will also receive an email notification with your exported environment link.

You can create as many environment archives as you want, but they will all be stored on your disk and will be charged according to your hosting provider's rates. If you don't need this file then you can delete it by clicking on the red cross button.

And this is all Your environment copy has been successfully exported, now you can proceed.importingGo to your preferred platform to complete the migration.