Thanks for getting in touch! I am sorry to say that the Web Deploy template does not support that scenario. And our changes in 3.0 also won’t support this.
I had a chat with a team mate though, and you could pretty easily deploy it with your current solution in the directory that you want in the same package, but of course that would mean that you would need to deploy them both at the same time.
The application in question has a separate life cycle to the parent application and is developed by a different team, I need to be able to deploy them individually.
Currently I am using FTP to do this, but FTP seems to take forever.
WebDeploy supports publishing to a virtual directory, is it a case of the template not providing the functionality I am looking for? Could I modify the template (if I knew what I was doing) to support my requirement, or is this something which simply cannot be done?
We actually aren’t sure, because we haven’t tried or tested the scenario, so our response was mostly ‘maybe?’.
As WebDeploy does support it, if you want to give it a shot and test, we would welcome a PR to add this functionality.
It looks like the WebDeploy step template does indeed support publishing to Azure Virtual Directories and I was just passing the wrong parameters.
Simply amending the website name to website/directory publishes to the virtual directory.
I was also adding the virtual directory to the publish URL, which is not required and this is why I was running into problems…phew.
It looks like in 3.0 there isn’t a textbox to enter the website/directory name, it is queried from the Azure subscription and provided in a drop down list, however I did read the blog post about reverting the feature back to 2.6 style so maybe it will work like phillip suggested.
Phil is using the web deploy step template which is still available and unchanged from 2.6. And the blog post is referring to the Azure template that we removed, not what is coming in 3.1.
3.1 is more of a hybrid between the two. The pre-release for 3.1 should be out next week.
So I had a chat to the dev who is working on the Azure changes and it still won’t be possible to use it and use a virtual directory with the 3.1 stuff.
But we do think it’s a valid feature and would mean less customers would need to use the web deploy template.
So I have created an issue you can track: https://github.com/OctopusDeploy/Issues/issues/1914
It might not make it to 3.1 but it might be shortly after.