Windows installer
| From: | Phil Driscoll | Date: | Tue, 12 Sep 2000 12:57:55 +0000 |
| Subject: | Windows installer | ||
| Groups: | php.qa | ||
| Request: | Send a blank email to php-qa+get-1294@lists.php.net to get a copy of this message | ||
Another question on the windows installer front.
For installing php with apache, clearly httpd.conf needs to be edited.
Whilst I have Apache on my development machine, I am a million miles away
from being an expert, so I'd be grateful if any experts could vet and modify
the following logic:
To add php (cgi) support to an existing httpd.conf file (which may or may
not already have php support added):
For every line which starts with ScriptAlias and contains php.exe, replace
the pathname with the pathname of the newly installed php.exe
If no lines contain php.exe, add the line
ScriptAlias /php "<PathToPHP>/php.exe"
after the first ScriptAlias line found. (Where do I put it if no ScriptAlias
lines are found?)
For each file extension specified by the installation wizard (eg .php,
.phtml etc)
If an addtype line already exists for the extension mapping it to
application/x-http-php3
do nothing, if is mapped to something else, change it to
application/x-http-php3, otherwise add an addtype entry for that extension
after the first addtype line found (Where do I put it if no AddType lines
are found?)
If the line
Action application/x-httpd-php3 /php/
exists, do nothing, otherwise add such a line (Where?)
NB I can see several shortcomings in the above scheme, but I don't know
Apache well enough to draw up a foolproof flowchart. I won't be offended if
the above is liberally shot down in flames - as long as the shooter tells me
what I need to do!
Cheers
PS is application/x-http-php3 something official or should it be deprecated
in favour of application/x-http-php ?
--
Phil Driscoll
Dial Solutions
+44 (0)113 294 5112
http://www.dialsolutions.com
http://www.dtonline.org