Seems like Octopus is only set up to deploy (IIS) Web Sites. Web Applications seem really rough. Our app is written as a Web Application, but the Web Application Octopus step doesn’t know anything about bindings.
So what I am finding I have to deploy an empty Web Site which just puts down what I want at the top level application where I set up the certificate binding, etc. This is going to be a pain because I have to figure out how to get my release of my project built using a version of another package which really doesn’t change much. By Default, it seems release 184.108.40.206 expects to find EmptyProject.220.127.116.11.zip in the library. Can I get it to always use EmptyProject.18.104.22.168 (or whatever the latest one is?)
After that, I need another step to deploy my main application using the Web Application Octopus step.
I tried using Website step only, installing the app in its “application” subdirectory, and using the “…” for the relative directory but that didn’t seem to work. Our app needs to be a full virtual app to leverage all the things that come with that.
I see there is a community “Create IIS Web Application”, but that still doesn’t manage any ssl bindings at the server level.
Is there a better way (without writing more powershell)?