Lines Matching refs:a
23 + Installing a PHP extension on Windows
35 + Where a configuration setting may be set
59 a web server and a web browser. You probably already have a web
61 have a web server (e.g. Apache on Linux and MacOS X; IIS on Windows).
62 You may also rent webspace at a company. This way, you don't need to
68 servers PHP has a direct module interface (also called SAPI). These
72 module support for your web server, you can always use it as a CGI or
84 extension. This is a completely different approach than writing web
96 » http://www.php.net/downloads.php. We recommend you to choose a
125 with a compile and configure process, or through various pre-packaged
128 package installation system. This can assist in setting up a standard
129 configuration, but if you need to have a different set of features
130 (such as a secure server, or a different database driver), you may need
133 whether somebody has already built a packaged version of PHP with the
137 * Basic Unix skills (being able to operate "make" and a C compiler)
153 a list of all available options along with short explanations running
170 We do not recommend using a threaded MPM in production with Apache 2.
173 with a threaded MPM
180 » Apache download site, and a fitting PHP version from the above
219 ./configure --help for a list of available options. In our example
220 we'll do a simple configure with Apache 2 and MySQL support.
273 rename or copy it to a .phps file:
285 Following the steps above you will have a running Apache2 web server
286 with support for PHP as a SAPI module. Of course there are many more
297 of this decision, and having at least a fair understanding of the
299 discusses MPMs in a great deal more detail.
307 To build a multithreaded version of Apache, the target system must
355 environment for the spawned processes. PHP will kill a child process
366 Lighttpd provides a program called spawn-fcgi to ease the process of
371 It is possible to spawn processes without spawn-fcgi, though a bit of
375 requests) each child will live. Here's a simple bash script to help
389 # Binding to a domain socket
451 3. gunzip php-x.x.x.tar.gz (if you have a .gz dist, otherwise go to
504 php.ini-values, for example you can set a
509 4. This is only needed if you want to configure a directory that only
510 consists of PHP scripts (same like a cgi-bin directory):
516 After that you can configure a directory in the Administration
531 6. To use PHP Authentication on a single directory, add the following:
546 WS/iPlanet/Netscape is a multithreaded web server. Because of that all
550 way to try this in the old PHP way with getenv() or a similar way
560 wanted to start, as a CGI script (a CGI script inside of the admin
584 directives which could interfere with yours. If you want to place a
589 create a PHP script which displays a directory listing and replace the
616 By default, PHP is built as both a CLI and CGI program, which can be
617 used for CGI processing. If you are running a web server that PHP has
629 If you have built PHP as a CGI program, you may test your build by
630 typing make test. It is always a good idea to test your build. This way
631 you may catch a problem with PHP on your platform early instead of
653 compile it, or install a pre-compiled binary.
679 contains the basic engine (plus gettext and iconv). Next, take a look
690 # /usr/local/sbin/phpxs -a mysql
693 # /usr/local/sbin/phpxs -a imap
694 (remove mysql as a test)
715 * The default install of Apache runs inside a » chroot(2) jail, which
717 will therefore need to create a /var/www/tmp directory for PHP
733 Older releases of OpenBSD used the FLAVORS system to compile up a
805 Second, before installing a package, it's wise to ensure the package
831 The examples will show a lot of packages including several PHP specific
878 There are a few pre-packaged and pre-compiled versions of PHP for Mac
879 OS X. This can help in setting up a standard configuration, but if you
880 need to have a different set of features (such as a secure server, or a
883 own software, it's worth checking whether somebody has already built a
899 with the default web server requires uncommenting a few lines in the
904 up a local development environment. It's highly recommended to always
908 further details. The following instructions are geared towards a
909 beginner with details provided for getting a default setup to work. All
910 users are encouraged to compile, or install a new packaged version.
922 Note: One way to open this is by using a Unix based text editor in
926 prompt for a password): sudo nano /private/etc/apache2/httpd.conf
933 2. With a text editor, uncomment the lines (by removing the #) that
968 location on Mac OS X is /usr/local/php/php.ini and a call to
969 phpinfo() will reveal this information. If a php.ini is not used,
979 7. Create a phpinfo() file
981 creating a file in the DocumentRoot with the following PHP code:
1012 * Installing a PHP extension on Windows
1021 » PECL is a repository of PHP extensions that are made available to you
1027 extension. Adjust accordingly. These instructions also assume a
1031 To be useful, a shared extension must be built, installed, and loaded.
1048 automatically, so in this case there is no need for a separate
1068 Installing a PHP extension on Windows
1070 On Windows, you have two ways to load a PHP extension: either compile
1071 it into PHP, or load the DLL. Loading a pre-compiled extension is the
1074 To load an extension, you need to have it available as a ".dll" file on
1081 To compile a standalone extension (aka a DLL file), please refer to
1097 Library (PECL) is a repository for PHP Extensions, providing a
1103 benefit from your time. A nice side effect is that you give them a good
1132 The most common way to load a PHP extension is to include it in your
1159 If you are using PHP with a web server, the location and format of the
1168 If the problem lies in a compile-time setting mismatch, you probably
1187 may install a beta package using the following command:
1191 You may also install a specific version using this variant:
1205 because you're behind a firewall, or it could be because the extension
1206 you want to install is not available as a PECL compatible package, such
1211 The phpize command is used to prepare the build environment for a PHP
1213 a directory named extname:
1237 php-config is a simple shell script for obtaining information about the
1282 You might find that you need to build a PECL extension statically into
1350 CGI or a server module, safe mode, etc.), and preferably enough code to
1357 If you think you have found a bug in PHP, please report it. The PHP
1364 Read the » How to report a bug document before submitting any bug
1376 * Where a configuration setting may be set
1398 major, minor and release versions. If there is a value for
1422 necessarily documented in this manual: for a complete list of
1428 ; any text on a line after an unquoted semicolon (;) is ignored
1451 a per-directory basis. These files are processed only by the
1477 Where a configuration setting may be set
1479 These modes determine when and where a PHP directive may or may not be
1481 For example, some settings may be set within a PHP script using
1511 configuration from within the Apache configuration files. For a listing
1513 have a look at the List of php.ini directives appendix.
1517 PHP_INI_ALL and PHP_INI_PERDIR type directives. To clear a
1524 Used to set a boolean configuration directive. Can be used only
1530 can not be overridden by .htaccess or ini_set(). To clear a
1534 Used to set a boolean configuration directive. This can not be
1559 on a per-directory basis using the Windows registry. The configuration
1577 If you are interested in a complete list of configuration settings on
1593 1. Why shouldn't I use Apache2 with a threaded MPM in a production
1596 3. Unix: I installed PHP, but every time I load a document, I get the
1603 6. Unix/Windows: I have installed PHP, but when I try to access a PHP
1604 script file via my browser, I get a blank screen.
1605 7. Unix/Windows: I have installed PHP, but when try to access a PHP
1606 script file via my browser, I get a server 500 error.
1612 9. Windows: I have installed PHP, but when I try to access a PHP
1614 specified CGI application misbehaved by not returning a complete
1629 Why shouldn't I use Apache2 with a threaded MPM in a production
1636 platform. It needs a working OS, a working web server and
1641 completely separate memory segments and a strong sandbox for
1645 If you want to use a threaded MPM, look at a FastCGI
1671 Unix: I installed PHP, but every time I load a document, I get the
1675 the case, and then try to reproduce the problem with a small
1677 you can provide a backtrace with your bug report to help the
1687 + If you are getting a core dump, gdb should inform you of this
1729 Unix/Windows: I have installed PHP, but when I try to access a PHP
1730 script file via my browser, I get a blank screen.
1731 Do a 'view source' in the web browser and you will probably find
1738 Unix/Windows: I have installed PHP, but when try to access a PHP script
1739 file via my browser, I get a server 500 error.
1741 see a sensible error message, from the command line, change to
1743 and run php -i. If PHP has any problems running, then a suitable
1744 error message will be displayed which will give you a clue as to
1745 what needs to be done next. If you get a screen full of HTML
1762 Windows: I have installed PHP, but when I try to access a PHP script
1767 returning a complete set of HTTP headers.
1771 all. To get to see a sensible error message, from the command
1774 running, then a suitable error message will be displayed which
1775 will give you a clue as to what needs to be done next. If you
1776 get a screen full of HTML codes (the output of the phpinfo()
1791 Internet Services Manager. If a script file does not exist
1792 then the server will return a 404 error instead. There is also
1799 Make sure any user who needs to run a PHP script has the rights
1803 And for IIS4 you need to tell it that PHP is a script engine.
1810 to 1 so be sure the directive isn't commented out (with a ;).
1819 To be sure your php.ini is being read by PHP, make a call to
1820 phpinfo(). Near the top, there will be a listing called
1823 a directory PATH exists, then it's not being read, and you
1827 If php.ini is being read and you're running PHP as a module,
1887 + Add a new line to the end of the file: set PHPRC=C:\php
