[Httpd Wiki] Update of "PHPOnUnix" by RichBowen

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Httpd Wiki" for change notification.

The "PHPOnUnix" page has been changed by RichBowen.
http://wiki.apache.org/httpd/PHPOnUnix

--------------------------------------------------

New page:
=== Note: This is pasted directly from PHP svn, and I'm aware that the formatting is wonky, but I need to go somewhere. I plan to fiddle with this this afternoon. This already contains several edits from what's on the official PHP site. RichBowen
===

     This section contains notes and hints specific to Apache 2.x installs
     of PHP on Unix systems.

     The <link xlink:href="&url.apache2.docs;">Apache Documentation</link>
     is the most authoritative source of information on the Apache 2.x server.
     More information about installation options for Apache may be found
     there.

    &install.snippet.apache2.compat;

     The most recent version of Apache HTTP Server may be obtained from
     <link xlink:href="&url.apache;">Apache download site</link>,
     and a fitting PHP version from the above mentioned places.
     This quick guide covers only the basics to get started with Apache 2.x
     and PHP. For more information read the
     <link xlink:href="&url.apache2.docs;">Apache Documentation</link>.
     The version numbers have been omitted here, to ensure the
     instructions are not incorrect. In the examples below, 'NN' should be
     replaced with the specific version of Apache being used.

     There are currently two versions of Apache 2.x - there's 2.0 and 2.2.
     While there are various reasons for choosing each, 2.2 is the current
     latest version, and the one that is recommended, if that option is
     available to you. However, the instructions here will work for either
     2.0 or 2.2.

     
Obtain the Apache HTTP server from the location listed above,
and unpack it:

     <example>
     <screen>
gzip -d httpd-2_x_NN.tar.gz
tar xvf httpd-2_x_NN.tar
     </screen>
     </example>
     </listitem>
     </orderedlist>
     </para>

     <example>
     <screen>

3.  gunzip php-NN.tar.gz
4.  tar -xvf php-NN.tar
5.  cd httpd-2_x_NN
6.  ./configure --enable-so
7.  make
8.  make install

    Now you have Apache 2.x.NN available under /usr/local/apache2,
    configured with loadable module support and the standard MPM prefork.
    To test the installation use your normal procedure for starting
    the Apache server, e.g.:
    /usr/local/apache2/bin/apachectl start
    and stop the server to go on with the configuration for PHP:
    /usr/local/apache2/bin/apachectl stop.

9.  cd ../php-NN

10. Now, configure your PHP.  This is where you customize your PHP
    with various options, like which extensions will be enabled.  Do a
    ./configure --help for a list of available options.  In our example
    we'll do a simple configure with Apache 2 and MySQL support.  Your
    path to apxs may differ, in fact, the binary may even be named apxs2 on
    your system. 

    
      ./configure --with-apxs2=/usr/local/apache2/bin/apxs --with-mysql

11. make
12. make install

    If you decide to change your configure options after installation,
    you only need to repeat the last three steps. You only need to
    restart apache for the new module to take effect. A recompile of
    Apache is not needed.
                
    Note that unless told otherwise, 'make install' will also install PEAR,
    various PHP tools such as phpize, install the PHP CLI, and more.
    
13. Setup your php.ini 
    
    cp php.ini-development /usr/local/lib/php.ini
          
    You may edit your .ini file to set PHP options.  If you prefer having
    php.ini in another location, use --with-config-file-path=/some/path in
    step 10.
    
    If you instead choose php.ini-production, be certain to read the list
    of changes within, as they affect how PHP behaves.

14. Edit your httpd.conf to load the PHP module.  The path on the right hand
    side of the LoadModule statement must point to the path of the PHP
    module on your system.  The make install from above may have already
    added this for you, but be sure to check.

      LoadModule php5_module modules/libphp5.so
 
15. Tell Apache to parse certain extensions as PHP.  For example, let's have
    Apache parse .php files as PHP.  Instead of only using the Apache AddType
    directive, we want to avoid potentially dangerous uploads and created
    files such as exploit.php.jpg from being executed as PHP.  Using this
    example, you could have any extension(s) parse as PHP by simply adding
    them.  We'll add .phtml to demonstrate.
            
      <FilesMatch \.php$>
          SetHandler application/x-httpd-php
      </FilesMatch>

    Or, if we wanted to allow .php, .php2, .php3, .php4, .php5, .php6, and
    .phtml files to be executed as PHP, but nothing else, we'd use this:

      <FilesMatch "\.ph(p[2-6]?|tml)$">
          SetHandler application/x-httpd-php
      </FilesMatch>
    
    And to allow .phps files to be handled by the php source filter, and
    displayed as syntax-highlighted source code, use this:

      <FilesMatch "\.phps$">
          SetHandler application/x-httpd-php-source
      </FilesMatch>

    mod_rewrite may be used To allow any arbitrary .php file to be displayed 
    as syntax-highlighted source code, without having to rename or copy it 
    to a .phps file:

      RewriteEngine On
      RewriteRule (.*\.php)s$ $1 [H=application/x-httpd-php-source]

    The php source filter should not be enabled on production systems, where
    it may expose confidential or otherwise sensitive information embedded in
    source code.

16. Use your normal procedure for starting the Apache server, e.g.:
   
      /usr/local/apache2/bin/apachectl start

          - OR -

      service httpd restart

   <para>
     Following the steps above you will have a running Apache2 web server with
     support for PHP as a <literal>SAPI</literal> module.  Of course there are
     many more configuration options available Apache and PHP.  For more
     information type <command>./configure --help</command> in the corresponding
     source tree.
    </para>
    <para>
     Apache may be built multithreaded by selecting the
     <filename>worker</filename> MPM, rather than the standard
     <filename>prefork</filename> MPM, when Apache is built. This is done by
     adding the following option to the argument passed to ./configure, in
     step 6 above:
    </para>
    <example>
    <screen>
     --with-mpm=worker
    </screen>
    </example>
    <para>
     This should not be undertaken without being aware of the consequences of
     this decision, and having at least a fair understanding of
     the implications. The Apache documentation
     regarding <link xlink:href="&url.apache2.mpm;">MPM-Modules</link>
     discusses MPMs in a great deal more detail.
    </para>
    <note>
     <para>
      The <link linkend="faq.installation.apache.multiviews">Apache MultiViews
      FAQ</link> discusses using multiviews with PHP.
     </para>
    </note>
    <note>
     <para>
      To build a multithreaded version of Apache, the target system must support threads.
      In this case, PHP should also be built with experimental
      Zend Thread Safety (ZTS). Under this configuration, not all extensions will be available.
      The recommended setup is to build Apache with the default
      <filename>prefork</filename> MPM-Module.