>
> Following discussion on irc, we're now waiting for Canada to come online
so
> that Frank can explain how he has his sapi installations working
without
> using PATH..
Canada or California thats almost the same exect for the temperature and
the amount of sunlight we get:-)
I'm using ispi only
Following discussion on irc, we're now waiting for Canada to come online so
that Frank can explain how he has his sapi installations working without
using PATH..
(in which case Edin's right - but what do the majority of new users install?
cgi or sapi?)
Here is the code which generates the Windows i
> > Yes; but apart from the Apache module case, the 'all in one
> dir' setup is
> > also valid for all uses, and far more simple. Is there a good
> reason why
> > we should advocate a more complex installation process simply to
> > accommodate PHP run as an Apache module?
>
> Its actually the othe
On Monday 21 June 2004 13:08, Steph wrote:
> > This is not really correct. First of all my instructions were
> > valid for all
> > web servers, including Apache, IIS, and even cgi/cli usage.
>
> Yes; but apart from the Apache module case, the 'all in one dir' setup is
> also valid for all uses, and
> This is not really correct. First of all my instructions were
> valid for all
> web servers, including Apache, IIS, and even cgi/cli usage.
Yes; but apart from the Apache module case, the 'all in one dir' setup is
also valid for all uses, and far more simple. Is there a good reason why we
shoul
On Monday 21 June 2004 12:01, Steph wrote:
> In order to install PHP so that it could be run as one of several PHP
> installations, you would install to a single directory, keeping the .ini
> and all other files related to that installation together, and configure
> your server to point toward the
ps what's PHPRC?
An environment varibale you can set to specify the path where
php[-sapiname].ini should be searched for.
Goba
