I've got the following websites set up:
- UpgradingSite - DefaultAppPool - d:\sites\upgrading - no host header (binding:80)
- Beta Site - BetaAppPool - d:\sites\beta - beta.mysite.com (binding:80)
The setup was made to have Beta Site serve when it's up, but when I disable the site, the upgrading site would take over. This also was done to have something nicer show up if the site ever accidentally got shut down.
Deploy sequence is as follows:
Beta SiteWebsite in IIS (Making the Upgrading page visible)
- Pull down latest changes
- Run build scripts
- Open IE & Warm up site. (2ish minutes)
Here's the problem:
I need a way to warm the site up while
Beta Site is not enabled, however I cannot actually hit the site (since it's disabled). I don't want the site to be enabled till it's available because we don't want our beta users to experience the long load associated with a warm up cycle.
There was a really cool IIS module that did something like this but it's been discontinued and no longer supported.
Let me clarify. When i meant disabled, I was talking the website entry (endpoint if you will), not the app pool.
The idea is to warm the site up while serving the updating page to users. Once the site is warm and good, then it would flip the switch to allow
beta.mysite.com to be served by the now warmed app pool.
I know about scripts to pre-warm by calling pages, but I cannot call pages if the endpoint is down (So the upgrade page/site would still serve users while the site is being warmed up by the script)