Support to deploy to a sub directory within an Azure WebApp
Sometimes users need to deploy content to a sub directory within an Azure WebApp, but they dont want to include the complete webapp on the NuGet package. Currently Octopus will delete anything that is not on the NuGet package.
A checkbox to avoid the files deletion and perhaps a field for "Custom Install dir" might be a good idea.
Jorge P. commented
Hi, our scenario is that we deploy multiple applications, under different web folders, so that they can be served from the same domain. But essentially, the requirement is the same: "be able to deploy to a defined sub directory".
This is an option in the Web Publishing Wizard, Connection step: Site name and Destination URL.
(more info, here: http://blogs.msdn.com/b/tomholl/archive/2014/09/22/deploying-multiple-virtual-directories-to-a-single-azure-website.aspx)
Jason Hedges commented
The big reason this is important is because of how Azure stores Web Jobs inside a Web App. Let's say you have a website and a console app that you want to run on a schedule. When you set this up in Azure Web Apps, you upload your website to Azure and then you upload your console app as a Web Job through the Azure portal. Azure stores the console app inside the App_Data directory of your website. The issue now is that when you re-deploy the website through Octopus Deploy, it deletes the App_Data directory if it doesn't exist as part of your site and deletes the console app (Web Job).