Azure Web Sites extensions: http://azure.microsoft.com/blog/2014/06/20/azure-web-sites-extensions/
How amazing would it be if you could add in an extension to your Azure Web Site that can connect to a OctopusDeploy server and register that website in a particular envionment with a particular role and have NuGet packages deployed to it?
It would be a much nicer ootb experience then the current Azure Web Sites Web Deploy library item (which is definitely awesome, but it's not very seamless).31 votes
We currently want to set features like the number of worker processes. It would be good to be able to set these up from Octopus instead of powershell.40 votes
Currently, OtcoPack considers a project a web application if a web.config file is found in its root. My stand-alone ServiceStack service project needs to have such a file when working with Razor support to enable intellisense support in VS. The web.config is never deployed however but OctoPack now deploys the project in web-style. That is, copying all binaries to the 'bin' sub directory while they should really go into the root. See https://github.com/OctopusDeploy/OctoPack/blob/fa2bbe0ce4b489316e090bf35f4d7d74d1d3a92a/source/OctoPack.Tasks/CreateOctoPackPackage.cs#L4631 vote
For PowerShell scripts it would be good to know the deployment start time.
This way later scripts can report how long a deployment took up to that point.
(A current workaround is to have a script run at the start that sets a variable for later use by other steps)1 vote
- Don't see your idea?