Sooner or later, every developer faces the necessity to branch the application he is working on, e.g. to try out new functionality before actually implementing it to the production. For such cases, the CirrusGrid PaaS provides a special option – environment cloning, which allows creating a complete copy of an already existing project in just a couple of clicks.
Also, if talking about more complex and sophisticated projects (which implies the involvement of the whole development team), multiple copies of your application (dedicated to a specific task) are recommended. The most common application lifecycle implementation involves the following stages:
Below, we’ll provide information on how to make an environment copy and some common use cases.
Note: Take into consideration the following specific points of environment cloning at CirrusGrid:
In order to create an environment copy, follow the next steps:
1. Click the appropriate Clone Environment button next to your environment, as it’s shown in the image below:
2. Within the appeared pop-up, specify a name for the environment clone or leave the default one and click Clone.
3. In a few minutes, the environment will be duplicated and ready for use.
Tip: For some specific cases, additional adjustments are required to make your environment copy operable:
Now, you can re-configure it, deploy new application versions, and apply any topology or application modifications – this won’t affect the original environment.
Consequently, you can use your environments in the following ways:
These use cases can help you to get the most from your original environment and its copy.
Powered by BetterDocs
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.