Environment Export

You may easily move environments across different cloud providers to find the one that best suits your needs, showcasing the platform’s flexibility. The two primary steps in this procedure are exporting the current environment (which we will go over in more depth below) and importing it into the intended PaaS installation. These simple, fast processes yield a replica of your environment operating on a different PaaS installation, complete with all its features.

How to Get Environmental Copy

Your environment’s contents, including deployed apps, connections to configuration archives, and topology settings, are all contained in a single.json file that can be exported. You can quickly download this file to your local computer to store it there or use it on another platform.

Go into your PaaS account and follow these steps to export a replica of your environment:

Step 1. Click on the “Settings” button for the environment you want to export (named “my-application” in our example).

Step 2. Within the Settings tab, go to the Export section and click on the “Export” button.

Step 3. Choose the data you wish to export from the Environment Export dialog that displays. To get a replica of the environment, make sure you check every box:

• Topology Settings: Includes environment configurations set through the Environment topology wizard (this is mandatory and enabled by default).
• Private Data: Includes files within the directories of your deployed applications and any private data stored within your database server(s).
• Configuration Files: Includes all files accessible via Configuration Manager on your dashboard, as well as settings of deployed GIT/SVN projects (e.g., repository links, access credentials, attached private SSH keys, etc.).

Once you have selected the data you want to export, click the “Export” button to proceed.

Step 4. Following the completion of the export procedure, a newly created clickable string with the export time/date attached will show up in the list of exported environment copies.

To download the compiled.json file containing the exported environment data to your local computer, choose this entry. As an alternative, you can right-click on it to copy the manifest file’s direct URL, which you can also use to import the file.

In addition, a link to the list of your exported environments will be sent to you via email.

And that’s it! The export of your environment copy has been completed. To finish the migration, you can now import it into the intended platform.