>
> 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
I am with Edin here, the basic instructions should be as simple as possible.
Running multiple php-versions is an advanced 'task' and IMHO not of interest
for someone who wants to start with php.
Something like 'running multiple versions' should be presented as FAQ.
Running php-gtk is covered by th
> > 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
gt; -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: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
On Monday 21 June 2004 12:34, Steph wrote:
> > Thats not as simple as it sounds. It is possible for php 5,
> > because there is
> > php.exe for the cli-version and php-cgi.exe for the cgi-version.
> > Unfortunately this is not true for php 4 versions, before we can instruct
> > people to dump all c
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
> Thats not as simple as it sounds. It is possible for php 5,
> because there is
> php.exe for the cli-version and php-cgi.exe for the cgi-version.
> Unfortunately this is not true for php 4 versions, before we can instruct
> people to dump all contents to e.g. c:\php. We have to instruct them, to
On Monday 21 June 2004 11:43, Jakub Vrana wrote:
> How we want the installation under Windows should work? The consensus is
> probably "copy everything (php.exe, php.ini, php*.dll, extension's and
> library's DLLs) in some directory (e.g. C:\PHP) and edit your server
> specific file". Is it politic
> > However, if you want to run PHP as an Apache module rather than
> as cgi, the
> > situation changes. In that case, Edin's solution is by far the
> easiest for
> > beginners.
>
> I know. What I am saying is that no application should be installed like
> that so we should rather try to change t
Steph wrote:
> Jakub: sadly, that's exactly what the consensus is NOT. That's what I'm
> fighting for ;)
I think it's consensus at least of the doc team (but maybe I'm wrong).
Everyone wants to install PHP in a single directory which allows you to
install multiple PHP versions on one machine, eas
ubject: Re: [PHP-DOC] help needed with windows install part of the PHP
> manual
>
>
> Hi,
> [...]
> > I don't think it matters where you put the information, so long
> as it's not
> > hidden away in a dusty corner where nobody ever finds it! What's wrong
&g
Hi,
[...]
> I don't think it matters where you put the information, so long as it's not
> hidden away in a dusty corner where nobody ever finds it! What's wrong
> with having a basic installation page with Edin's advice, and a more
> flexible guide for multiple installations nearby?
As long as we
asiest for
beginners.
-Original Message-
From: Steph [mailto:[EMAIL PROTECTED]
Sent: 21 June 2004 10:50
To: Jakub Vrana; [EMAIL PROTECTED]
Subject: RE: [PHP-DOC] help needed with windows install part of the PHP
manual
Jakub: sadly, that's exactly what the consensus is NOT. Tha
Jakub: sadly, that's exactly what the consensus is NOT. That's what I'm
fighting for ;)
> -Original Message-
> From: Jakub Vrana [mailto:[EMAIL PROTECTED]
> Sent: 21 June 2004 10:43
> To: [EMAIL PROTECTED]
> Subject: Re: [PHP-DOC] help needed with windows in
Friedhelm Betz wrote:
> I am with Edin here, the basic instructions should be as simple
> as possible.
> Running multiple php-versions is an advanced 'task' and IMHO not
> of interest
> for someone who wants to start with php.
> Something like 'running multiple versions' should be presented as FAQ
How we want the installation under Windows should work? The consensus is
probably "copy everything (php.exe, php.ini, php*.dll, extension's and
library's DLLs) in some directory (e.g. C:\PHP) and edit your server
specific file". Is it politically correct to try changing the PHP itself
to work with
On Monday 21 June 2004 11:08, Steph wrote:
> > I would not complicate the issue. Our current instructions also
> > assume that
> > there is only a single php install on the machine and I think we
> > should keep
> > it that way. The goal should be to get users up and running with
> > php quickly.
>
> I would not complicate the issue. Our current instructions also
> assume that
> there is only a single php install on the machine and I think we
> should keep
> it that way. The goal should be to get users up and running with
> php quickly.
> They can later go with the advanced stuff like multipl
On Sunday 20 June 2004 14:12, Steph wrote:
> This is fine if you only want one PHP setup. Speaking with my PHP-GTK hat
> on, it's not that straightforward... most PHP-GTK users will have both a
> server-based installation of some kind _and_ a cli-based installation. I
> think it's safe to say tha
he Apache 2 module.
> -Original Message-
> From: Edin Kadribasic [mailto:[EMAIL PROTECTED]
> Sent: 20 June 2004 07:24
> To: Gabor Hojtsy; PHPdoc
> Subject: Re: [PHP-DOC] help needed with windows install part of the PHP
> manual
>
>
> If you don't want to clutter you
If you don't want to clutter your system with php files the following
instructictions should work with all webservers.
1. Unpack php distro to a dir say 'c:\php'
2. Create php-.ini in your windows folder based on php.ini-dist
3. Add c:\php to your path (this may require reboot depending on windows
> You said you didn't used to have this problem with PHP4. That's why I'm
> asking, how did you have it set up with PHP4?
I don't remember of saying that :) but I don't remember how I had PHP 4
configured (I've migrated a long time ago).
In PHP 4, I also had the php.ini in the windows folder
Re: [PHP-DOC] help needed with windows install part of the PHP
> manual
>
>
> > ok, so what worked when php4apache2.dll was loaded?
> I'm using PHP 5 :)
>
> whay I'm using:
>
> C:\php (all contents from the zip + PEAR packages)
>
> C:\windows\php.ini (a
> > In apache2\bin: copy of php5ts.dll, copy of php.ini
>
> I don't have any file in the apache dir...
> I've made a test, and if you copy the php.ini file to the apache dir, it
> will parse it, instead of the php.ini file in the windows folder.
I can't reproduce this. I suspect you still have a
> ok, so what worked when php4apache2.dll was loaded?
I'm using PHP 5 :)
whay I'm using:
C:\php (all contents from the zip + PEAR packages)
C:\windows\php.ini (and pear.ini) (without copying this, the apache doesn't
parse the php.ini)
C:\windows\system32\libmysql.dll (without this the mysql exte
ok, so what worked when php4apache2.dll was loaded?
> -Original Message-
> From: Nuno Lopes [mailto:[EMAIL PROTECTED]
> Sent: 19 June 2004 18:29
> To: [EMAIL PROTECTED]; PHP-DOC
> Subject: Re: [PHP-DOC] help needed with windows install part of the PHP
> manual
>
> Can you tell me exactly what your layout is/was for Apache 1.3.* please?
I
> never loaded a module into that..
I've never used apache 1.3.x on windows. I've always used apache 2.
Can you tell me exactly what your layout is/was for Apache 1.3.* please? I
never loaded a module into that..
> -Original Message-
> From: Nuno Lopes [mailto:[EMAIL PROTECTED]
> Sent: 19 June 2004 18:25
> To: [EMAIL PROTECTED]; PHP-DOC
> Subject: Re: [PHP-DOC] help need
> In system path (e.g. system32): the underlying extension libs (e.g.
> libmysqli.dll) - the alternative is to hold them locally whereever you
want
> them, but if you do this you'd need a separate copy in apache2\bin and
> anywhere a php.exe needs them.
>
> In apache2\bin: copy of php5ts.dll, copy
nder PHP 4? Is it a bug or a
feature, and if so which version's correct?
-Original Message-
From: Steph [mailto:[EMAIL PROTECTED]
Sent: 19 June 2004 16:37
To: Nuno Lopes; Gabor Hojtsy
Cc: PHPdoc
Subject: RE: [PHP-DOC] help needed with windows install part of the PHP
manual
following m
following minor discussion with Nuno and a lot of fiddling around here..
Not being an Apache expert, I'm failing to understand why the apache2handler
will only load php5apache2.dll (along with _all_ its friends, including
php.ini) if it's in the apache\bin dir (directly, and don't mess with it!).
ps what's PHPRC?
An environment varibale you can set to specify the path where
php[-sapiname].ini should be searched for.
Goba
This means that if we suggest people to replicate the PHP 5 package
structure with PHP 4 (move the contents of the dlls folder and the sapi
folder into the root PHP folder), and place php.ini there, then that
should work without and special PATH settings either for PHP 4 or PHP 5.
I wonder why this
> > I have no clue why Nuno reports that it does not work for PHP 5.
Probably
> > the clue's in 'set PATH'. There's no reason to set PATH unless you're
doing
> > something very strange with PHP. I don't have any PHP-related
environmental
> > variables set. The php-specific shared libraries (e.g
> This means that if we suggest people to replicate the PHP 5 package
> structure with PHP 4 (move the contents of the dlls folder and the sapi
> folder into the root PHP folder), and place php.ini there, then that
> should work without and special PATH settings either for PHP 4 or PHP 5.
> I wonde
My setups (8 of the 9 I have here): php.exe (whichever one I'm using is
named 'php.exe' in all cases, whether cli or cgi) is in the same directory
as php.ini, php*ts.dll, and the external shared libraries (e.g.
libmysqli.dll) needed to support whatever extensions that particular version
of php need
ps what's PHPRC?
-Original Message-
From: Steph [mailto:[EMAIL PROTECTED]
Sent: 19 June 2004 14:17
To: Gabor Hojtsy; PHPdoc; Wez Furlong; [EMAIL PROTECTED]
Subject: RE: [PHP-DOC] help needed with windows install part of the PHP
manual
> - the current Windows docs suggest users
> - the current Windows docs suggest users to copy files to the windows
> and system32 folders
>
> - people (Daniel Convissor) report that it is possible to not do
> this, but set PATH to include the PHP folder and the dlls
> folder below the PHP folder (for PHP 4) + set PHPRC
>
>
Hi Frank, Wez, and all!
Wez promised us that he will help rewamp the Windows installation part,
but he does not reply to our mails. Our dilemma is the following:
- the current Windows docs suggest users to copy files to the windows
and system32 folders
- people (Daniel Convissor) report that
43 matches
Mail list logo
