Deployment slots enable us to perform more robust deployment workflows than deploying our website directly to production. When we create an Azure website, we are automatically provisioned with a production slot that represents our live website. With each deployment slot, we can create up to four additional deployment slots (for a total of five) that we can swap with the production slot (or even with other non-production slots). When we swap, the site content and certain slot configurations are exchanged with no downtime. This is useful in
the following scenarios:
■ Staged deployment In a staged deployment, we deploy to a non-production slot that is acting as a staging environment. In this environment, we test whether the website is working as expected, and when we are satisfied that it is, we swap the production slot with the staging slot, making the staged content and certain parts of the configuration the new production website.
■ Incremental deployment If our website deployment includes incremental steps that we need to take post-deployment, we can deploy to a non-production slot, make those changes, and then swap with the production slot to make the updated website live.
■ Rolling back deployment If, after swapping a non-production slot into production, we need to roll back the deployment, we can swap the production slot again with the slot that contains the previous production content and configuration, thereby rolling back the deployment.
the following scenarios:
■ Staged deployment In a staged deployment, we deploy to a non-production slot that is acting as a staging environment. In this environment, we test whether the website is working as expected, and when we are satisfied that it is, we swap the production slot with the staging slot, making the staged content and certain parts of the configuration the new production website.
■ Incremental deployment If our website deployment includes incremental steps that we need to take post-deployment, we can deploy to a non-production slot, make those changes, and then swap with the production slot to make the updated website live.
■ Rolling back deployment If, after swapping a non-production slot into production, we need to roll back the deployment, we can swap the production slot again with the slot that contains the previous production content and configuration, thereby rolling back the deployment.
No comments:
Post a Comment