That’s very interesting. I’m wondering if something is happening on they Sitefinity side as all the deploy package step is doing is extracting the files included in the package, performing any required config file transformations (e.g. path to SQL database) then copying them to the final destination.
You can see that in the logs,
07:24:45 Verbose | Extracting package to: C:\Octopus\Applications\Development\SitefinityWebApp._APPNAME\188.8.131.52_1
07:24:50 Info | Transforming 'C:\Octopus\Applications\Development\SitefinityWebApp._APPNAME\184.108.40.206_1\web.config' using 'C:\Octopus\Applications\Development\SitefinityWebApp._APPNAME\220.127.116.11_1\web.Development.config'.
07:24:51 Info | Copying package contents to 'C:\inetpub\wwwroot\APPNAME'
So I’m very curious as to why the mappings have disappeared. As a test are you able to perform functionally the same process manually? You should be able to copy the files from
'C:\inetpub\wwwroot\APPNAME' and see if the mappings are removed as part of that process.
I can’t see anywhere in the logs where we would be interacting with IIS, and that step in particular (
deploy a package) definitely won’t. Are you also able to check and make sure that there is nothing in Sitefinity that might be resetting your IIS settings?
Thanks Bil, I look forward to hearing from you,