3 ms·
You can easily configure different things of IIS/ASP.NET like Port Bindings, App Domains, Config Transforms, SSL Sites, etc. We also use it to bundle and deploy
by mythz 12y ago
You can easily configure different things of IIS/ASP.NET like Port Bindings, App Domains, Config Transforms, SSL Sites, etc. We also use it to bundle and deploy out-of-project artefacts.
One nice feature is that it keeps all your releases and can easily redeploy a previous known working configuration.
- junto 12y agoDon't forget rollback. That has saved us a number of times. One of the things I like about Octopus is rather than deploy over the existing instance it deploys a version alongside. Then if everything is hunky-dory with the deployment process it simply tweaks IIS to point at the new deloyment folder. I don't believe that MSDeploy does that. I think it just overwrites the existing source. Also, can MSDeploy deploy to multiple servers? Anyway, Octopus is very neat and tidy. We also recycle app pools and restart windows services using Powershell scripts as deployments out of Octopus for some legacy apps that don't support distributed caching and the cache is stale. It's quick an dirty but it works.