Install and configure PHP 56 + Nginx 18

PHP

Download PHP 5.6 (VC11 x86 Non Thread Safe), unzip it to any directory, copy the file php.ini-development and rename it to php.ini.

I did not modify the contents of the php.ini file, and the subsequent tests passed. If you want to change it in the future, you can refer to http://php.net/manual/zh/install.windows.manual.php

Nginx

to download Nginx 1.80 and unzip it in any directory. Open its configuration file conf/nginx.conf and find the following paragraph:

#location ~ \.php$ {##}

Delete all the # signs in front and replace this line:

fastcgi_param  SCRIPT_FILENAME  /scripts$fastcgi_script_name;

with:

fastcgi_param  SCRIPT_FILENAME  $document_root$fastcgi_script_name;

That is, replace /scripts with $document_root

The modified complete configuration block is:

# pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000#
location ~ \.php$ {
    root           html;
    fastcgi_pass   127.0.0.1:9000;
    fastcgi_index  index.php;
    fastcgi_param  SCRIPT_FILENAME$document_root$fastcgi_script_name;
    include        fastcgi_params;
}

Or the whole block can be changed to the following:

# pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000#
location ~ \.php$ {
    root           html;
    fastcgi_pass   127.0.0.1:9000;
    fastcgi_index  index.php;
    include        fastcgi.conf;
}

Run it

Then create info.php in the Nginx Root directory (html directory) The content of the file is as follows:

phpinfo();

Start Nginx (if it has already been started, shut it down and restart it).

Start php-cgi (listen to the local port 9000):

cd path-to-php-home
php-cgi-b127.0.0.1:9000

If an error is reported, you need to install the VC2012 (VC11) runtime library first: http://www.microsoft.com/en-us/download/details.aspx ?id=30679

Open the browser access address http://127.0.0.1/info.php

Nginx first receives the request, and then forwards it to php-cgi, which parses and executes the PHP code and returns it to Nginx. Finally Return to the browser.

If the link can be opened normally and a lot of PHP-related information is displayed (as shown in the picture below), it means the configuration is successful.

This is the first time that I (Liigo) have displayed this interface by myself, and it feels quite comfortable.

PHP-FPM or spawn-fcgi or php-cgi?

Looking at online analysis, PHP-FPM is much better than spawn-fcgi, and PHP-FPM has been officially integrated by PHP 5.3.3+, so spawn is eliminated first -fcgi, PHP-FPM preferred.

But, but, to enable PHP-FPM, you have to compile the PHP source code yourself, ./configure --enable-fpm.... This task is still very troublesome in the Windows environment, so I will give it up for now.

What to do next? I didn't know what to do at first. Later, through Internet searches, I found out that the php-cgi program can also be used as a FastCGI server. So I settled for the next best thing and chose php-cgi.

Conclusion, you can temporarily use php-cgi in the development environment, but the deployment environment must be PHP-FPM in the future.

PHP 5 or PHP 7?

PHP 7 is very good and powerful, but it has not been officially released yet, and it will take transition time for various frameworks and codes to support it. So for the time being, let’s stick to PHP 5, otherwise novices will be helpless when faced with subtle compatibility issues.