Here’s what I’m thinking
- I don’t want to include IT/Ops scripts in my application code (i.e. the PreDeploy.ps1 etc in the root of the package). I’d like that to be something shared across applications so if I change something about how the web server is configured I don’t need to update 30 files in 30 different projects
- At the same time I want to be able to keep things as simple as possible. I’d like to use my PackageName as the IIS web site name, app pool name etc. So I can’t add a powershell step (to create the IIS site if needed etc) before the deploy step as the package isn’t defined yet.
So I’d like to either define my (shared) scripts as part of the deploy within Octopus