{"id":41094,"date":"2024-05-13T13:45:17","date_gmt":"2024-05-13T13:45:17","guid":{"rendered":"https:\/\/accuweb.cloud\/resource\/?post_type=faq&p=41094"},"modified":"2026-02-19T05:43:42","modified_gmt":"2026-02-19T05:43:42","slug":"swap-domains","status":"publish","type":"faq","link":"https:\/\/accuweb.cloud\/resource\/articles\/swap-domains","title":{"rendered":"Swap Domains"},"content":{"rendered":"

Swap Domains<\/h2>\n

When you’re working on a project, you’ll eventually need to make upgrades or changes. Before making any big moves in the live environment, it’s crucial to thoroughly test everything.<\/p>\n

Luckily, with AccuWeb.Cloud, you can do this testing in a separate environment. Once your new version is ready, you can simply swap domains<\/strong> between your testing area and your live project. This allows for an instant switch to the new version without any hassle.<\/p>\n

This feature is really helpful because it means you don’t have to go through the whole process of updating your live site. You don’t have to worry about extra setups or any potential downtime either. Plus, you can still keep the previous version of your site just in case you need to roll back quickly.<\/p>\n

It’s important to note that the Swap Domains feature works specifically with bound domains<\/strong>. If you’re looking to swap URLs for environments that have public IPs as an entry point (attached to the application server or load balancer), you’ll need to use the swap external IPs method or adjust the appropriate records in your domain registrar.<\/p>\n

Create Test Environment<\/h2>\n

First, you’ll need to locate your production environment, where your application is currently running and where you want to apply updates. For the purposes of this example, let’s refer to this environment as “production.”<\/p>\n

\"Running<\/a><\/p>\n

\n

Note:<\/strong> Keep in mind that this production environment must be associated with a custom domain that is bound to it (for instance, “production.com”). This custom domain will later be swapped with a different environment.\"Add<\/a><\/p>\n<\/div>\n

<\/div>\n

Next, you’ll want to click on the “Open in Browser<\/strong>” button or access your application via its custom domain to ensure everything is functioning as expected before proceeding with any updates.<\/p>\n

\"Access<\/a><\/p>\n

Now, proceed to clone this environment<\/strong> to automatically generate an identical copy, encompassing all deployed packages, databases, and other components. We’ll designate this duplicate environment as “testing<\/strong>.”<\/p>\n

\"Clone<\/a><\/p>\n

After cloning the environment, click on the “Open in Browser<\/strong>” button for the cloned environment to ensure that everything is functioning properly. This step is crucial to verify that the cloned environment replicates the functionality of the production environment accurately.<\/p>\n

\"Cloned<\/a><\/p>\n

Now, you can add new features, customize settings, and apply updates as needed \u2013 all without disrupting your original setup.<\/p>\n

<\/div>\n\t\t
\n\t\t\t
\n \n
\n
\n
\n \n \t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t <\/div>\n <\/div>\n <\/div>\n <\/section>\n \t\t<\/div>\n\t\t\n
<\/div>\n

Update Application<\/h2>\n

First, make the necessary changes to the cloned environment. You can do this either directly through the dashboard or by deploying the new version of your project. If you need assistance with your project adjustments, refer to the following documentation guides:<\/p>\n