Perhaps it would be wise to recommend that inexperienced users stay with a
CGI/CLI install. I don't see why anyone would want to run PHP as an Apache
module on a win32 box unless they were running a server 'for real' as
opposed to for home development purposes, so the related speed issues
shouldn't really be a concern at that level.
I seem to remember having trouble with Apache configuration last time I
installed it and tried to load CGI - I've a feeling the options for doing
that are no longer part of the distributed httpd.conf, which could be why
everyone's so keen to load PHP as an Apache module in the first place.
Does anyone know if there's some deprecation in progress there? - I'm
talking about 1.3.* here, but the same applies for Apache 2. I haven't
actually tried to load PHP as CGI in Apache 2 at all, to date - don't use
it, generally.
Ignore my paths, they aren't typical!
Configuration for running PHP as CGI (Apache 1.3.*):
# Directory Index
<IfModule mod_dir.c>
DirectoryIndex index.html index.htm index.php
</IfModule>
# ScriptAlias
ScriptAlias /php/ "C:/php/php5latest/"
# Document types
<IfModule mod_mime.c>
AddType application/x-httpd-php .php
Action application/x-httpd-php "/php/php.exe"
</IfModule>
Configuration for running PHP as Apache module (Apache 2.*):
# Dynamic Shared Object (DSO) Support
LoadModule php5_module \sandbox\php5\release_ts\php5apache2.dll
# AddType
AddType application/x-httpd-php .php
> -----Original Message-----
> From: Friedhelm Betz [mailto:[EMAIL PROTECTED]
> Sent: 21 June 2004 11:41
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Cc: Edin Kadribasic; Gabor Hojtsy
> Subject: Re: [PHP-DOC] help needed with windows install part of the PHP
> manual
>
>
> On Monday 21 June 2004 12:11, Steph wrote:
> > Maybe we're approaching this in the wrong way. Maybe we should have one
> > set of instructions (Jakub's, Frank's and mine) for installing PHP as
> > cgi/cli and another (Edin's) for installing PHP as an Apache
> module. The
> > FAQ could then sensibly contain something about multiple
> installations when
> > PHP is already running as an Apache module.
> >
> > Does that make more sense?
>
> As long as we can not find a basic solution that works for all
> kind of setups,
> maybe. But I still prefer the most simple, pragmatic one,
> unfortunately this
> kind of solution seems far away, till now.
>
> It will be hard for newbies to switch with your suggested instructions?
>
> Friedhelm
