installation software
| From: | Phil Driscoll | Date: | Mon, 21 Aug 2000 18:15:40 +0000 |
| Subject: | installation software | ||
| Groups: | php.qa | ||
| Request: | Send a blank email to php-qa+get-899@lists.php.net to get a copy of this message | ||
Hi
I've been polluting my brain with Visual Basic and COM in order for the
Windows installation software to be able to automatically configure IIS.
I now have a short Visual Basic Script which takes as command line
parameters the location of php.exe and a list of file extensions to map (eg
.php, .phtml etc).
I can write the appropriate values into the IIS metabase and the
configuration seems to work. What the software does is take the existing
script map, remove any entries for file extensions in the supplied list (eg
.php) and then create a new entry for each file extension in the list.
What I need is some advice/discussion about which node or nodes of the
metabase to edit.
The potential nodes are:
WWW service master properties
Web sites (on unique IP addresses and via host header redirection)
Virtual Directories
Applications
Directories
Files
In all cases, the settings here are inherited by any new nodes created, but
not any existing ones, so, for example if I edit the WWW service master
properties, it essentially has no effect, because the web sites underneath
already have their own script map settings.
Possible strategies include:
Only setting the script map for the first web site (usually labelled Default
web site in the management console).
Walking through all nodes, and anywhere there is a script map, add the php
stuff to the node.
Although the first option only works well for machines with one web site and
no other defined script maps, it is pretty safe.
The second option allows me to make a complete mess of an existing
configuration, with the possibility of causing security problems.
Any thoughts on what I should do?
--
Phil Driscoll
Dial Solutions
+44 (0)113 294 5112
http://www.dialsolutions.com
http://www.dtonline.org