Release 0.8.0: Windows installer, twelve fixes from a real Server 2019 install, operator docs

deploy/windows/web.config

@@ -67,15 +67,28 @@
       It ships DISABLED because it needs the URL Rewrite module; enabled without
       it, IIS returns HTTP 500.19 ("configuration section not well-formed").
 
+      There is deliberately NO <allowedServerVariables> block below. Setting a
+      server variable requires that variable to be allowed, but the section
+      system.webServer/rewrite/allowedServerVariables ships with
+      overrideModeDefault="Deny", so declaring it in an application's own
+      web.config is refused outright: IIS answered 500.52 with error 0x80070021,
+      "this configuration section cannot be used at this path", BEFORE it ever
+      reached httpPlatformHandler - so python was never launched and the stdout
+      log stayed empty, which looks like an application fault and is not one.
+
+      The installer instead allows the single variable at server level, which
+      grants exactly HTTP_X_FORWARDED_FOR rather than unlocking the section and
+      letting every site on the machine declare arbitrary server variables.
+
       The installer handles both: -ClientIpSource direct installs URL Rewrite
-      from the bundle and enables this; -ClientIpSource proxy leaves it alone.
-      By hand: install URL Rewrite, then delete the two marker lines below.
+      from the bundle, allows the variable, and enables this; -ClientIpSource
+      proxy leaves it alone. By hand: install URL Rewrite, run
+        appcmd set config /section:system.webServer/rewrite/allowedServerVariables ^
+          /+"[name='HTTP_X_FORWARDED_FOR']" /commit:apphost
+      then delete the two marker lines below.
     -->
     <!-- SHOPDB-CLIENTIP-BEGIN
     <rewrite>
-      <allowedServerVariables>
-        <add name="HTTP_X_FORWARDED_FOR" />
-      </allowedServerVariables>
       <rules>
         <rule name="Set X-Forwarded-For" stopProcessing="false">
           <match url=".*" />