0

I've seen this: Zero downtime uploads / Rollback in IIS, but for a small site, ARR seems like overkill. I'm wondering if it'd work to have a web.config like this

<?xml version="1.0" encoding="UTF-8"?>
<configuration><system.webServer><rewrite><rules>
  <rule name="Rewrite to current production version">
    <match url="(.*)" /><action type="Rewrite"
      url="production-version-0/{R:1}" />
  </rule></rules></rewrite></system.webServer>
</configuration>

To deploy, drop in the directory production-version-1, and then over-write web.config so that it points to the new version. This is a PHP site. Will I regret doing it this way?

Community
  • 1
Chuck
  • 3

2 Answers2

1

Apart from the obvious penalty of having a rewrite in every request (also for static content) it also might give problems with self referencing scripts. Scripts that ask PHP for their filename (e.g. $_SERVER['SCRIPT_NAME']) will get the rewritten URL and not the URL that is shown in the user's browser.

Marco Miltenburg
  • 1,121
0

it can not be. Point.

See, your problem is that with one system only you never reach zero downtime because sometimes something faults and / o you need a reset due to patching. Point.

Playing around with this requirement wont get you anywhere. You need 2-3 systems at least, and then you can use NLB easily, so no need to pull anything.

TomTom
  • 52,109
  • 7
  • 59
  • 142