1. Add software dependencies

Before we add Ondřej Surý’s PPA, we must make sure the add-apt-repository binary is available on our operating system. This binary is included in the python-software-properties Ubuntu package. Type this command into your terminal application and press Enter. Enter your account password if prompted:

sudo apt-get install python-software-properties

This command installs the Python Software Properties package that includes the add-apt-repository binary. Now we can add the custom PPA.

2. Add ppa:ondrej/php5-5.6 PPA

This PPA expands Ubuntu’s available software selection beyond the default Ubuntu software repositories. Type this command into your terminal application and press Enter. Enter your account password if prompted:

sudo add-apt-repository ppa:ondrej/php5-5.6

This command adds the Ondřej Surý PPA to Ubuntu’s list of software sources. It also downloads the PPA’s GPG public key and appends it to our local GPG keyring. The GPG public key enables Ubuntu to verify that the packages in the PPA have not been tampered with since they were built and signed by their original author.

Ubuntu caches the list of all available software. When we add new software sources, we need to refresh Ubuntu’s cache. Type this command in your terminal application and press Enter. Enter your account password if prompted:

sudo apt-get update

3. Install PHP

We can now use Ubuntu’s aptitude package manager to install the latest PHP stable release from the Ondřej Surý PPA. Before we do, it is important to know which PHP packages are available and what they do. PHP is distributed in two forms. One form is a CLI package that enables you to use PHP on the command line (we will use this one). There are several other PHP packages that integrate PHP with the Apache or nginx web servers (we discuss these in Chapter 7). For now, we’ll stick with the PHP CLI package.

First, let’s install the PHP CLI package. Type this command in your terminal application and press Enter. Enter your account password if prompted:

sudo apt-get install php5-cli

The Linux package manager also contains packages for individual PHP extensions that can be installed separately. Let’s install a few of those now. Type this command in your terminal application and press Enter. Enter your account password if prompted:

sudo apt-get install php5-curl php5-gd php5-json php5-mcrypt php5-mysqlnd

Verify PHP was installed successfully with this terminal command:

php -v

This command should output something similar to:

PHP 5.5.11-3+deb.sury.org~trusty+1 (cli) (built: Apr 23 2014 12:15:16)
Copyright (c) 1997-2014 The PHP Group
Zend Engine v2.5.0, Copyright (c) 1998-2014 Zend Technologies
    with Zend OPcache v7.0.4-dev, Copyright (c) 1999-2014, by Zend Technologies

1. Add the EPEL repository

Let’s tell our CentOS/RHEL system to use the EPEL software repository. Type these commands into your terminal application one-by-one, and press Enter after each command. Enter your account password if prompted:

sudo rpm -Uvh \
  http://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-5.noarch.rpm;
sudo rpm -Uvh \
  http://rpms.famillecollet.com/enterprise/remi-release-7.rpm;

These commands add the third-party EPEL and remi software repositories to our CentOS/RHEL system. You should now see epel.repo and remi.repo files in the /etc/yum.repos.d directory.

2. Install PHP

Now we’ll install the latest PHP version from the EPEL and remi repositories. As I mentioned earlier in the Ubuntu PHP installation, PHP is distributed in two forms. One form is a CLI package that enables you to use PHP on the command line. For now, we’ll stick with the PHP CLI package.

First, let’s install the PHP CLI package. Type this command in your terminal application and press Enter. Enter your account password if prompted.

sudo yum -y --enablerepo=epel,remi,remi-php56 install php-cli

Next, let’s install a few additional PHP extensions. You can search for a complete list of PHP extensions with the yum package manager. Type this command into your terminal application and press Enter:

yum search php

Once you find a list of PHP extensions, install them as I do in this example. Your package names might be different:

sudo yum -y --enablerepo=epel,remi,remi-php56 \
     install php-gd php-mbstring php-mcrypt php-mysqlnd php-opcache php-pdo

The important takeaway from this command is the --enablerepo option. This option tells yum to install the specified software packages from the EPEL, remi, and remi-php56 repositories. Without this option, yum only references its default software sources.

Verify that PHP was installed successfully. Type this command in your terminal application and press Enter:

php -v

This command should output something similar to:

PHP 5.6.3 (cli) (built: Nov 16 2014 08:32:30)
Copyright (c) 1997-2014 The PHP Group
Zend Engine v2.6.0, Copyright (c) 1998-2014 Zend Technologies
    with Zend OPcache v7.0.4-dev, Copyright (c) 1999-2014, by Zend Technologies

Install

Download the MAMP package (.pkg) installer from http://www.mamp.info, and double-click the MAMP package installer. Follow the on-screen instructions.

When the MAMP installer finishes, find the MAMP application in your /Applications folder and launch it by double-clicking its application icon. After MAMP opens, click the Start Servers button to start the Apache and MySQL servers (Figure A-2). It’s really that simple.

Figure A-2. MAMP interface

What about PHP?, you ask. MAMP embeds PHP inside of the Apache web server using the mod_php Apache module. Without getting into too much detail, you can use PHP if the Apache web server is running. We discuss PHP deployment strategies in Chapter 7.

After you start the Apache and MySQL servers, open your web browser and go to http://localhost:8888. You should see a MAMP welcome page if MAMP is successfully installed.

The Apache web server typically listens for connections on port 80. MAMP, however, runs Apache on port 8888. Likewise, MySQL typically listens for connections on port 3306. MAMP, however, runs MySQL on port 8889. You can change MAMPs default ports in the MAMP application preferences. MAMP’s Apache web server document root is /Applications/MAMP/htdocs. Any PHP files in this directory can be accessed in a web browser at http://localhost:8888.

If you will use MAMP a lot, go into the MAMP application preferences (Figure A-3) and make sure Start Servers when starting MAMP is checked. Then add the MAMP application to your OS X account’s Login Items. This will start MAMP’s Apache and MySQL servers automatically when you log in to OS X.

Figure A-3. MAMP application preferences

Extend

It is possible to download MAMP add-ons that provide different PHP versions for your local MAMP installation. MAMP is updated frequently and most likely comes bundled with the latest PHP version. But if for whatever reason it doesn’t, or if you need an older PHP version, go to the MAMP website and download the PHP version you need.

Limitations

The MAMP free version provides only one Apache virtual host, and it does not let you easily modify PHP’s configuration or extensions. MAMP is very basic and provides only the bare necessities for PHP development on OS X.

MAMP provides a paid “Pro” version that lets you create multiple Apache virtual hosts, easily edit your php.ini configuration file, and fine-tune PHP extensions. MAMP Pro is nice, don’t get me wrong. But instead of forking out a good bit of money for MAMP Pro, you’re better off learning a few command-line fundamentals so you can use the excellent Homebrew package manager instead.

XCode command-line tools

Before we can install Homebrew, we must first install the XCode Command-Line Tools provided (for free) by Apple, Inc. These command-line tools include the gcc compiler (among other tools) needed by Homebrew to build and install software packages. If you are running OS X Mavericks 10.9.2 or newer, open the OS X Terminal application, type this command, and press Enter:

xcode-select --install

This command opens this modal window shown in Figure A-4.

Figure A-4. Installing XCode command-line tools

Click Install to begin installing the XCode Command-Line Tools. Click Agree when the software license agreement appears. After the XCode Command-Line Tools software is installed, click Done and continue to the next step.

If you are using an older version of OS X, you must log into the Apple Developer Portal to download and run a standalone XCode Command-Line Tools package (.pkg) installer.

Install

After you install the XCode Command-Line Tools, type this command in the OS X Terminal application and press Enter:

ruby -e "$(curl -fsSL https://raw.github.com/Homebrew/homebrew/go/install)"

Directory permissions

Homebrew downloads and ferments software in the /usr/local/Cellar directory. It symlinks installed software binaries to the /usr/local directory. Your OS X user account must be able to access the /usr/local directory to use software installed with the Homebrew package manager.

Let’s make sure your OS X user account owns the /usr/local directory. Type this command into the OS X Terminal application and press Enter. Enter your administrator password if prompted:

sudo chown -R `whoami` /usr/local

The chown command means “change the owner” of the specified directory, the -R command flag means “make this change recursively to all subdirectories” of the specified directory, and the whoami argument is dynamically substituted with your OS X user account name. After you run this command, your OS X user account will own (and therefore have access to) the /usr/local directory.

Environment PATH

Next, add the /usr/local directory to your OS X environment PATH. The environment PATH is a list of directories to be searched when you execute software using only the software’s name instead of the software’s absolute filesystem path. For example, if I execute wget, OS X will search all directories on my environment PATH for the wget software. Otherwise, I’d have to type /usr/local/wget every time I want to use wget. Type this command into the OS X Terminal application and press Enter:

echo 'export PATH="/usr/local/bin:$PATH"' >> ~/.bash_profile

Tap formulae repositories

Before we install PHP with Homebrew, we must tap additional repositories that contain PHP-related formulae that do not exist in the default Homebrew repository.

First, we’ll tap the homebrew/dupes repository. This repository contains formulae for software that already exists on OS X. This repository, however, contains newer software versions than OS X. Type this command in the OS X Terminal application and press Enter:

brew tap homebrew/dupes

Next, we’ll tap the homebrew/versions repository. This repository contains multiple versions of existing OS X software. Type this command in the OS X Terminal application and press Enter:

brew tap homebrew/versions

Finally, we’ll tap the homebrew/php repository. This repository contains PHP-related formulae that might not be included in the default Homebrew repositories. The default Homebrew software repository is not maintained by PHP developers. This repository is, and it includes software appropriate for PHP developers. Type this command in the OS X Terminal application and press Enter:

brew tap homebrew/php

Install PHP

So far, we’ve installed the Homebrew package manager, configured filesystem permissions, updated the environment PATH, and tapped into additional formulae repositories. Now it’s time to install PHP. There are Homebrew formulae for each PHP version and each PHP version’s extensions. Homebrew provides a very simple way to search for available formulae. Type this command in the OS X Terminal application and press Enter:

brew search php

You should see a lengthy list of Homebrew PHP formulae. Find the latest stable PHP version in the formulae list (PHP 5.5.x will be named php55, PHP 5.6.x will be named php56, and so on). I’ll pick php56 since PHP 5.6.x is the latest stable version (as of December 2014). Type this command in the OS X Terminal application and press Enter:

brew install php56

Installation may take a while, so feel free to grab a coffee and check back in a few minutes. After the PHP software package is installed, you can confirm the installation by executing php -v in the OS X Terminal application; this command outputs the full name and version number of the PHP interpreter installed by Homebrew.

Install PHP extensions

Homebrew lets you install PHP extensions separately from the PHP interpreter. You can search for PHP extensions just as you searched for PHP previously. Assuming you chose php56, type this command in the OS X Terminal application and press Enter:

brew search php56

You should see a lengthy list of PHP 5.6 extensions prefixed with php56-. After you find the extensions you want, type this command in the OS X Terminal application and press Enter. Swap the formulae in this example with the extension formulae you want to install:

brew install php56-intl php56-mcrypt php56-xhprof

The Homebrew package manager is much more powerful than what I’ve shown here. Type brew into the OS X Terminal application and press Enter to see a complete list of Homebrew commands. You can also read the complete Homebrew documentation online at http://brew.sh.

The src/ directory

First, we create a src/ directory in our home folder. This folder will contain the source code that we download from PHP.net. We cd into the src/ directory so that it becomes our current working directory:

mkdir ~/src;
cd ~/src;

Download the source code

Next, we use wget to download the PHP source code as a tar.gz archive. The downloaded file will be located at ~/src/php.tar.gz:

wget -O php.tar.gz http://www.php.net/get/php-5.6.3.tar.gz/from/this/mirror

Extract the PHP source code archive with the tar command, and cd into the unarchived source code directory:

tar -xzvf php.tar.gz;
cd php-*;

Configure PHP

We’ve downloaded the PHP source code. Now we need to configure it. Before we do, we must install a few software dependencies. How do I know what dependencies to install? I run the ./configure command (see the next subsection) until it works. When the ./configure command fails due to a missing software dependency, it indicates what software is missing. Install the missing dependency and rerun the ./configure command. Rinse and repeat until it works.

Luckily for you, I’ve already figured out what software dependencies are needed for the PHP ./configure command we’ll be using. Let’s install these software dependencies now. I use commands for both Ubuntu/Debian and CentOS/RHEL Linux distributions; use the commands appropriate for your Linux distribution.

Build essentials

We’ll need these fundamental software binaries to build PHP on your operating system. These binaries include gcc, automake, and other fundamental development software:

# Ubuntu
sudo apt-get install build-essential;

# CentOS
sudo yum groupinstall "Development Tools";

libxml2

We’ll need the libxml2 library. This is used by PHP’s XML-related functions:

# Ubuntu
sudo apt-get install libxml2-dev;

# CentOS
sudo yum install libxml2-devel;

OpenSSL

We’ll need the openssl library. This is required to enable HTTPS stream wrappers in PHP, which is kind of important, right?

# Ubuntu
sudo apt-get install libssl-dev;

# CentOS
sudo yum install openssl-devel;

Curl

We’ll need the libcurl library. This is required by PHP’s Curl functions:

# Ubuntu
sudo apt-get install libcurl4-dev;

# CentOS
sudo yum install libcurl-devel;

Image manipulation

We’ll need the GD, JPEG, PNG, and other image-related system libraries. Fortunately, all of these are bundled into a single package. These are required to manipulate images with PHP:

# Ubuntu
sudo apt-get install libgd-dev;

# CentOS
sudo yum install gd-devel;

Mcrypt

We’ll need the mcrypt system library to enable PHP’s Mcrypt encryption and decryption functions. For whatever reason, there is no default CentOS Mcrypt package. We’ll need to supplement the default CentOS packages with the third-party EPEL package repository to install Mcrypt:

# Ubuntu
sudo apt-get install libmcrypt-dev;

# CentOS
wget http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm;
sudo rpm -Uvh epel-release-6*.rpm;
sudo yum install libmcrypt-devel;

The ./configure command

Now that our software dependencies are installed, let’s configure PHP. Type the following ./configure command in your Terminal application and press Enter:

./configure
    --prefix=/usr/local/php5.6.3
    --enable-opcache
    --enable-fpm
    --with-gd
    --with-zlib
    --with-jpeg-dir=/usr
    --with-png-dir=/usr
    --with-pdo-mysql=mysqlnd
    --enable-mbstring
    --enable-sockets
    --with-curl
    --with-mcrypt
    --with-openssl;

This is a lengthy command with a lot of options. Don’t be overwhelmed. Each command option has a specific purpose. You can find a list of all available options with ./configure --help. We’ll go through this ./configure command line by line so you know exactly what it does:

--prefix=/usr/local/php5.6.3

The --prefix option defines the path to a filesystem directory that will contain the compiled PHP binaries, includes, libraries, and configuration files. I prefer to keep my custom PHP build and related files together in a single parent directory for the sake of organization. Your user account will need permission to write to this directory. If you don’t have write permission to /usr/local, you can set the --prefix to a directory in your user account’s home folder instead (e.g., ~/local/php-5.5.13). Regardless, make sure the --prefix directory exists before you run the ./configure command.

--enable-opcache

The --enable-opcache option enables PHP’s built-in bytecode caching system. You will most always want to enable this. The performance benefits are tremendous.

--enable-fpm

The --enable-fpm option enables the built-in PHP FastCGI Process Manager. This lets you run PHP as a FastCGI process that is accessible via a TCP port or a local Unix socket. FPM is fast becoming the preferred way to run PHP (especially with the nginx web server). If in doubt, I recommend you enable this option.

--with-gd

The --with-gd option lets PHP interface with your operating system’s GD image-manipulation library. You will want to enable this option if you plan on using PHP to manipulate images.

--with-zlib

The --with-zlib option lets PHP interface with your operating system’s Zlib library. Zlib is a data-compression library that is needed by the GD image library to create and manipulate PNG image data. This option is required if you use the --with-gd option.

--with-jpeg-dir

The --with-jpeg-dir option specifies the path to the filesystem directory that contains the JPEG libraries. This option is required if you use the --with-gd option.

--with-png-dir

The --with-png-dir option specifies the path to the filesystem directory that contains the PNG libraries. This option is required if you use the --with-gd option.

--with-pdo-mysql=mysqlnd

The --with-pdo-mysql option instructs PHP to enable the PDO database abstraction API for the MySQL database using PHP’s own native MySQL driver. If you use MySQL, you’ll want to enable this option.

--enable-mbstring

The --enable-mbstring option instructs PHP to enable multibyte (read “Unicode”) string support. You’ll most always want to enable this option.

--enable-sockets

The --enable-sockets option instructs PHP to enable network socket support so that you can talk with remote machines via TCP sockets. You’ll most always want to enable this option.

--with-curl

The --with-curl option lets PHP interface with your operating system’s curl library. This lets you use PHP’s curl functions to send and receive HTTP requests. You’ll most always want to enable this option.

--with-mcrypt

The --with-mcrypt option lets PHP interface with your operating system’s mcrypt library for data encryption and decryption. Although this option is by no means required, it is used by a growing number of PHP components. I strongly recommend you enable this option.

--with-openssl

The --with-openssl option lets PHP interface with your operating system’s openssl library. This is required to use PHP’s HTTPS stream wrapper. Although this option is technically optional, it’s really not. Make Edward Snowden proud. Enable this option.

Make and install PHP

Configuring PHP and installing its software dependencies was the hard part. It’s all downhill from here. Assuming the ./configure command executed successfully, type this command in your terminal application and press Enter:

make && make install

This will compile PHP and may take a while. Now is a good time to grab a coffee or two. Eventually the command will finish and PHP will be installed. That wasn’t too bad, right?

The compiled PHP binaries are available in the bin/ directory beneath your --prefix directory. The php-fpm binary is available in the sbin/ directory beneath your --prefix directory. Be sure the bin/ and sbin/ directories are added to your system’s environment PATH so you can reference the php binary by name instead of absolute path.

Create the php.ini file

Let’s not forget about our php.ini file. This may not be created automatically. The PHP GitHub repository has a php.ini preconfigured for local development. Our php.ini file should exist in the lib/ directory beneath your --prefix directory. Let’s create it now. Type the following commands into your terminal application and press Enter after each command.

First, cd into our PHP installation’s lib/ directory. This path may be different if you used a different --prefix path in your ./configure command:

cd /usr/local/php5.6.3/lib

Next, download the PHP.ini file from PHP’s GitHub repository into a file named php.ini:

curl -o php.ini \
  https://raw.githubusercontent.com/php/php-src/master/php.ini-development

That’s it. We’re all set to execute PHP files with the newly installed php interpreter. We talked more about the php-fpm binary when we discussed PHP deployment strategies in Chapter 7.