Deployment Process
- Application Cloning – Make a replication of the application so that the original project will remain unaffected
- Asset Optimization – Perform a series of best practices optimizations on all resources. Users can choose which optimization to perform on the resources.
- Asset Preparation – redirecting the static into the cloud. This will allow developers to develop application with little thought of how the application will be deployed. The Cloud Manager will hand the preparation of assets
- Asset Versioning – Makes versioning of static resources simple so that application can be easily rolled back and minimize out-of-date assets in the new applications.
- Cloud Loading – Asset that are appropriate for the cloud will be uploaded and configured gain the highest performances.
Deployment Wizard
Starting the Deployment process can be done by either selecting the New -> Project -> "Cloud Deployer" or right clicking on the asset in selecting "Deploy into the Cloud". The user is then given a series of wizard that walk them through the deployment process.Once the "Finish" button is pressed the user will be given a screen that shows them the stage of the deployment and any error, warning or information that would be help to the users. Once the new project has been created and optimized the user will given an option to deploy the static resources into the Cloud. The Cloud Deployer will take care of all the settings necessary to make the artifacts available at this point. Users can choose to deploy and not make immediately available. If this option is selected the users will need to use the S3 Service View to set the privilege to read_only for everyone.
