On Monday 02 August 2004 12:14, Gabor Hojtsy wrote: > > I only had a brief look, but following comes to my mind: > > Manual Installation Steps: > > I would like to advice people to use php-(sapiname).ini or at least > > mention this somewhere. > > I would second that the SAPI specific ini file names need more promotion! > > > I like to suggest that setup of a valid php.ini file is moved to the > > server specific instructions. Because one can run php just fine without > > any ini-file, you need this mainly for enabling extensions, or setting > > specific instructions. > > It is better to document it in the manual part IMHO, as php.ini settings > are not server specific.
At least for the CGI setup they are, some need cgi.force_redirect set to 0. But we have a faq entry on this http://www.php.net/manual/en/ini.sect.path-directory.php#ini.cgi.force-redirect and linking this from server specific instructions is perhaps enough? If we want to promote SAPI specific ini file names, setup of php-(sapiname).ini should be in the server specific instructions. Why? I believe a typical newbie should do (outlined in brief): 1.) download php4/5 2.) unzip at some location (we should use that locations from main/config.w32.h: c:\php4 and c:\php5) 3.) what webserver? setup of that server (Apache1/2, IIS/PWS, Omni, Sambar.... 4.) test the server with phpinfo 5.) which ini filename? php-cgi.ini/php-apache.ini ....... 6.) right place for ini-file, PHPRC, PHPIniDir, PATH, Systemroot, install it, adjust cgi.force_redirec if needed. 7.) do 4.) again, check if right ini is used 8.) install extensions/ change ini settings. 9.) do 4.) > > Windows and PWS 4 or newer > > > > Instructions for php 5 are missing, filenames imply its for php 4 only > > (e.g.: pws-php4cgi.reg) > > > > Same for Windows NT/2000/XP and IIS 4 or newer (e.g: php4isapi.dll) > > These should be PHP 5 ready, sure! Yep;-) Friedhelm -- http://www.jungle-world.com/
