title: How do I gracefully take a web app offline during Octopus deployment?
body: <p>I was a bit remiss to find that Octopus, as amazing as it is, doesn't do anything cute or clever about shutting down your web app before it is upgraded.</p>
  
  <p>In our solution we have two web apps (a website and a separate API web app) that rely on the same database, so while one is being upgraded the other is still live and there is potential that web or API requests are still being serviced while the database is being upgraded.</p>
  
  <p>Not clean!</p>
  
  <p>Clean would be for Octopus to shut down the web apps, wait until they are shut-down and then go ahead with the upgrade, bring the app pools back online once complete.</p>
  
  <p>How can that be achieved?</p>