#php versions

PHP stands for Hypertext Preprocessor, is a widely used scripting language for web development. Since its inception in the mid-1990s, PHP has evolved significantly, adapting to changing technology trends and incorporating new features and improvements. In this blog, we will delve into the evolution of PHP, exploring the significant versions, modern development practices, and the future outlook of this dynamic language. As a PHP developer or someone interested in web development, understanding the evolution of PHP is crucial to stay up to date with the latest advancements and make informed decisions when building web applications. So, let's embark on a journey through the evolution of PHP and discover how it has shaped the world of web development.

Evolution of PHP Versions

Since its inception, PHP has undergone several major releases, each bringing significant improvements and new features to the language. Let's explore the evolution of PHP versions and understand the key advancements in each iteration.

PHP 1: 

The first version of PHP was released, providing basic functionality for web development.

PHP 2: 

The second version of PHP introduced support for dynamic web pages and database connectivity.

PHP 3: 

Support for object-oriented programming, which greatly enhanced the language’s capabilities.

PHP 4: 

Introduced several new features, including support for XML, improved database connectivity, and the ability to create web services.

PHP 5:

Enhanced error handling mechanisms, Improved performance, and memory management.

PHP 7:

Introduction of the Zend Engine 3, Addition of scalar type declarations for function arguments and return values, Introduction of anonymous classes, and closure improvements.

PHP 8:

Introduce JIT compiler, Addition of union types, allowing variables and function return types to accept multiple possible types. Enabling metadata to be attached to classes, methods, and properties.

The evolution of PHP versions demonstrates the continuous effort to enhance the language's performance, flexibility, and functionality. Each release has introduced features and improvements to make PHP more robust, secure, and developer-friendly.

Modern PHP Development Practices

With the evolution of PHP, modern development practices have emerged, enabling developers to write more efficient, maintainable, and scalable code. Let's explore some of the critical practices that have gained popularity in the PHP ecosystem:

Object-Oriented Programming (OOP):

Embracing OOP principles allows developers to organize code into reusable objects and classes.

Encapsulation, inheritance, and polymorphism facilitate modular and structured code development.

OOP promotes code reusability, separation of concerns, and easier maintenance.

PHP Frameworks:

Utilizing PHP frameworks, such as Laravel, Symfony, or CodeIgniter, streamlines development by providing pre-built components, libraries, and MVC (Model-View-Controller) architecture.

Frameworks facilitate rapid development, code organization, and everyday tasks like routing, database handling, and user authentication.

They promote best practices and standardize coding conventions, leading to cleaner and more maintainable codebases.

Dependency Management:

Adopting dependency management tools like Composer simplifies the integration of external libraries and packages into PHP projects.

Composer allows developers to define project dependencies and automatically manages their installation and updates.

It promotes code reuse, reduces wheel reinvention, and ensures project dependencies are easily maintainable.

Unit Testing:

Writing unit tests using frameworks like PHPUnit helps ensure code correctness, identify and prevent bugs, and facilitate code refactoring.

Unit tests provide a safety net when making changes, allowing developers to validate that existing functionality remains intact.

Test-driven development (TDD) is an approach that emphasizes writing tests before writing the actual code, leading to more reliable and maintainable software.

PSR Standards:

The PHP Standards Recommendations (PSR) are guidelines and standards established by the PHP community to promote interoperability and consistency in PHP projects.

Adhering to PSR standards improves code readability, collaboration, and compatibility across different frameworks and libraries.

Following PSR standards ensures that codebases are well-structured, easily maintainable, and accessible to a broader community of developers.

Continuous Integration and Deployment (CI/CD):

Implementing CI/CD pipelines, utilizing tools like Jenkins or GitLab CI, automates the building, testing, and deployment of PHP applications.

Continuous integration ensures that code changes are regularly integrated into a shared repository, preventing integration issues.

Continuous deployment automates deploying code to production environments, ensuring a streamlined release process.

Future Outlook of PHP

PHP has come a long way since its inception, and its future looks promising as it continues to evolve and adapt to the ever-changing web development landscape. Let's explore some key aspects that shape the future outlook of PHP:

Performance and Scalability:

With the introduction of the Just-In-Time (JIT) compilation in PHP 8, performance improvements have already been made.

Further advancements in PHP's runtime engine and optimizations are expected, enhancing its performance and scalability for handling modern web applications.

Language Enhancements:

PHP's development community is continuously working on introducing new language features and improvements to enhance developer productivity and code maintainability.

Future PHP versions may introduce additional language constructs, syntactic sugar, and language-level abstractions to simplify everyday development tasks.

Security Enhancements:

PHP developers increasingly focus on security practices to protect applications from vulnerabilities and attacks.

The PHP community actively releases security updates, and future versions are expected to include enhanced security features and improved default security configurations.

Support for Modern Web Standards:

PHP is expected to continue adapting to modern web standards and technologies, such as HTTP/2, WebSockets, and Progressive Web Applications (PWAs).

Frameworks and libraries will continue to evolve to support these standards, enabling developers to build cutting-edge web applications.

Integration with Emerging Technologies:

PHP will likely integrate with emerging technologies like machine learning, artificial intelligence, and the Internet of Things (IoT).

Integration with these technologies will open up new possibilities for PHP developers to build intelligent and data-driven applications.

Community Growth and Collaboration:

The PHP community continues to grow, fostering collaboration, knowledge sharing, and open-source contributions.

PHP conferences, meetups, and online forums provide platforms for developers to connect, learn from each other, and stay updated with the latest trends and advancements.

Compatibility and Legacy Support:

PHP remains committed to backward compatibility, ensuring existing PHP applications can be migrated and maintained without significant disruptions.

Future PHP versions will likely strike a balance between introducing new features and maintaining compatibility with earlier versions.

Conclusion

PHP has evolved significantly over the years, transforming from a simple scripting language to a powerful and versatile tool for web development. In this blog, we explored the evolution of PHP versions, modern PHP development practices, adapting to modern PHP development tools, and the future outlook of PHP.

Are you looking for a trusted partner to develop your software projects?

#Php versions how to

#Php versions upgrade

#Php versions full

Create a Site Backupīefore you switch PHP versions, make a backup of your site. Pressable customers, don’t worry… We’ve got you covered! We always offer the latest version of PHP that’s compatible with WordPress. You’ll need to check with your hosting provider to see what versions they support. You can also see your PHP version from your WordPress admin by going to “Tools” and clicking on “Site Health.” Pressable customers can easily check the PHP versions you’re running on all of your sites within the MyPressable Control Panel.

#Php versions how to

Here’s how to check your current version of PHP and the steps to follow when upgrading to the latest version.

#Php versions upgrade

Not only will your PHP version get regular bug fixes and patches, but your web host may require you to upgrade your PHP before they can offer their own support. New versions of PHP include updated features, some of which your plugin and theme developers will likely want to use, such as those introduced in PHP version 8.0. It’s like leaving your front door open while you’re on vacation and hoping no one steals your stuff. If you’re using a version of PHP that has reached its end of life, you’re opening your site up to major security threats. Newer versions of PHP will help your site run faster. Outdated PHP versions can slow a site down. It’s extremely risky to use an unsupported version of PHP to run your website. 28, 2022, which may expose sites using it to unpatched security vulnerabilities. Security support for version 7.4 will end Nov. The latest version of PHP, 8.1 was released Nov. The PHP Foundation will offer critical security updates but nothing else.Īfter three years, the PHP version will officially reach its end of life and no longer be updated or supported.

#Php versions full

During this period, regular updates address any bugs or security issues.Īt the end of the two years of full support, PHP offers one additional year of security support. The PHP development team fully supports each PHP version for two years after its initial release. You’ll see why in the next section when we review why you want to upgrade. WordPress will most likely work with an older version of PHP as long as it’s greater than 5.6.20. WordPress PHP Version RequirementsĪs of the release of WordPress 6.0 in May 2022, WordPress requires servers to run PHP version 7.4 or greater. When we talk about PHP versions, we’re talking about what version of PHP your web server is working from. Your web server runs a program that interprets and executes the PHP code. Your WordPress core system files, themes, and plugins include PHP code. Processing the PHP code ultimately renders your WordPress page or post. WordPress is a PHP-powered content management system. More than three-fourths of all websites use PHP. PHP is a scripting language for web development. In this post, we share why you should upgrade your site’s PHP and the steps for managing PHP upgrades. But checking your PHP version is a lot like testing your smoke detectors – you know you’re supposed to do it at least twice a year, but you probably wait until that annoying chirp lets you know the batteries are dead.ĭon’t wait for your site to break before you give attention to your PHP versions. PHP versions can significantly impact your website’s performance and security. You know you’re supposed to keep your WordPress system up-to-date, but when was the last time you checked your PHP version?

PHP version paths under Plesk ODIN

The different PHP versions unter Plesk ODIN are situated in /opt/plesk/php/. So the PHP paths are for example:

 /opt/plesk/php/5.2/bin/php

/opt/plesk/php/5.3/bin/php

/opt/plesk/php/5.4/bin/php

/opt/plesk/php/5.5/bin/php

/opt/plesk/php/5.6/bin/php

/opt/plesk/php/7.0/bin/php

Which PHP versions are available depends on the versions installed.

You can see your installed versions under https://yourdom…

New Post has been published on http://goo.gl/I1HOa

PHP 5.5.0 drops Windows XP support and adds Optimizer

Recently, PHP professionals have released the latest version that is 5.5 of the most famous and popular scripting language. Comprised with many new features and functionalities also well known as generators, it let developers to deploy such simple co-routines. This new version has Zend optimizer and introduces a password hashing function available to easily generate secure and safe salted passwords and run a block of code useful for different applications for better stability.

New Post has been published on http://mocco.sk/tips-on-how-to-use-php-4-4-9-fastcgi-with-apache-ispconfig-3-debian-wheezy/

Tips on how to Use PHP 4.4.9 (FastCGI) With Apache & ISPConfig 3 (Debian Wheezy)

Version 1.0 Author: Falko Timme <ft [at] falkotimme [dot] com> Follow me on Twitter Last edited 06/18/2013

Since ISPConfig 3.0.5, it is possible to use multiple PHP versions on one server and select the optimal PHP version for a website. If you have some very old websites on your server, they might not work with PHP5, but only with PHP4. This tutorial shows how to build PHP 4.4.9 as a FastCGI version for use with Apache2 on a Debian Wheezy server. This PHP version can be used together with the default PHP (installed through apt) in ISPConfig.

I do not issue any guarantee that this will work for you!

1 Preliminary Note

PHP-FPM is not available for PHP4, therefore I just describe how to build a FastCGI version of PHP4. FastCGI is available only for Apache servers, therefore you cannot use it with nginx..

2 Building PHP 4.4.9 (FastCGI)

Install the prerequisites for building from source code:

apt-get install build-essential

PHP 4.4.9 will not compile with modern OpenSSL versions, therefore we need to install an older OpenSSL version (0.9.8x) first:

cd /tmp wget http://www.openssl.org/source/openssl-0.9.8x.tar.gz tar xvfz openssl-0.9.8x.tar.gz cd openssl-0.9.8x ./config –prefix=/usr/local/openssl-0.9.8 make make install

Download and extract PHP 4.4.9:

mkdir /opt/phpfcgi-4.4.9 mkdir /usr/local/src/php4-build cd /usr/local/src/php4-build wget http://de.php.net/get/php-4.4.9.tar.bz2/from/this/mirror -O php-4.4.9.tar.bz2 tar jxf php-4.4.9.tar.bz2

cd php-4.4.9/

Create some necessary symlinks:

ln -s /usr/lib/x86_64-linux-gnu/libjpeg.so /usr/lib/ ln -s /usr/lib/x86_64-linux-gnu/libpng.so /usr/lib/ ln -s /usr/lib/x86_64-linux-gnu/libmysqlclient.so.18 /usr/lib/ ln -s /usr/lib/x86_64-linux-gnu/libexpat.so /usr/lib/ ln -s /usr/lib/x86_64-linux-gnu/libmysqlclient.so /usr/lib/libmysqlclient.so mkdir /usr/kerberos ln -s /usr/lib/x86_64-linux-gnu /usr/kerberos/lib

Next we must disable the functions mysql_drop_db and mysql_create_db because otherwise you will get these errors when you try to build PHP 4.4.9:

error: undefined reference to ‘mysql_drop_db’ error: undefined reference to ‘mysql_create_db’

Open /usr/local/src/php4-build/php-4.4.9/ext/mysql/php_mysql.c…

vi /usr/local/src/php4-build/php-4.4.9/ext/mysql/php_mysql.c

… and go to line 1131. From there on, comment out both functions:

[...] /*PHP_FUNCTION(mysql_create_db) { zval **db, **mysql_link; int id; php_mysql_conn *mysql; switch(ZEND_NUM_ARGS()) { case 1: if (zend_get_parameters_ex(1, &db)==FAILURE) { RETURN_FALSE; } id = php_mysql_get_default_link(INTERNAL_FUNCTION_PARAM_PASSTHRU); CHECK_LINK(id); break; case 2: if (zend_get_parameters_ex(2, &db, &mysql_link)==FAILURE) { RETURN_FALSE; } id = -1; break; default: WRONG_PARAM_COUNT; break; } php_error_docref(NULL TSRMLS_CC, E_NOTICE, "This function is deprecated, please use mysql_query() to issue a SQL CREATE DATABASE statement instead."); ZEND_FETCH_RESOURCE2(mysql, php_mysql_conn *, mysql_link, id, "MySQL-Link", le_link, le_plink); PHPMY_UNBUFFERED_QUERY_CHECK(); convert_to_string_ex(db); if (mysql_create_db(&mysql->conn, Z_STRVAL_PP(db))==0) { RETURN_TRUE; } else { RETURN_FALSE; } }*/ /* }}} */ /* {{{ proto bool mysql_drop_db(string database_name [, int link_identifier]) Drops (delete) a MySQL database */ /*PHP_FUNCTION(mysql_drop_db) { zval **db, **mysql_link; int id; php_mysql_conn *mysql; switch(ZEND_NUM_ARGS()) { case 1: if (zend_get_parameters_ex(1, &db)==FAILURE) { RETURN_FALSE; } id = php_mysql_get_default_link(INTERNAL_FUNCTION_PARAM_PASSTHRU); CHECK_LINK(id); break; case 2: if (zend_get_parameters_ex(2, &db, &mysql_link)==FAILURE) { RETURN_FALSE; } id = -1; break; default: WRONG_PARAM_COUNT; break; } php_error_docref(NULL TSRMLS_CC, E_NOTICE, "This function is deprecated, please use mysql_query() to issue a SQL DROP DATABASE statement instead."); ZEND_FETCH_RESOURCE2(mysql, php_mysql_conn *, mysql_link, id, "MySQL-Link", le_link, le_plink); convert_to_string_ex(db); if (mysql_drop_db(&mysql->conn, Z_STRVAL_PP(db))==0) { RETURN_TRUE; } else { RETURN_FALSE; } }*/ /* }}} */ [...]

Install the prerequisites for building PHP5 (in our case this also covers the prerequisites for building PHP4):

apt-get build-dep php5

Configure and build PHP 4.4.9 as follows (you can adjust the ./configure command to your needs, take a look at

./configure –help

to see all available options; if you use a different ./configure command, it is possible that additional libraries are required, or the build process will fail):

./configure \ –prefix=/opt/phpfcgi-4.4.9 \ –with-pdo-pgsql \ –with-zlib-dir \ –with-freetype-dir \ –enable-mbstring \ –with-libxml-dir=/usr \ –enable-soap \ –enable-calendar \ –with-curl \ –with-mcrypt \ –with-zlib \ –with-gd \ –with-pgsql \ –disable-rpath \ –enable-inline-optimization \ –with-bz2 \ –with-zlib \ –enable-sockets \ –enable-sysvsem \ –enable-sysvshm \ –enable-pcntl \ –enable-mbregex \ –with-mhash \ –enable-zip \ –with-pcre-regex \ –with-mysql=/usr \ –with-mysql-sock=/var/run/mysqld/mysqld.sock \ –with-jpeg-dir=/usr \ –with-png-dir=/usr \ –enable-gd-native-ttf \ –with-openssl=/usr/local/openssl-0.9.8 \ –with-openssl-dir=/usr/local/openssl-0.9.8 \ –with-libdir=/lib/x86_64-linux-gnu \ –enable-ftp \ –with-imap \ –with-imap-ssl \ –with-kerberos \ –with-gettext \ –with-expat-dir=/usr \ –enable-fastcgi

The last switch (–enable-fastcgi) makes sure this PHP version will work with FastCGI.

make make install

Copy php.ini to the correct location:

cp /usr/local/src/php4-build/php-4.4.9/php.ini-recommended /opt/phpfcgi-4.4.9/lib/php.ini

That’s it – we will now add the APC module to our PHP 4.4.9 installation:

cd /tmp wget http://pecl.php.net/get/APC-3.0.19.tgz tar xvfz APC-3.0.19.tgz cd APC-3.0.19 /opt/phpfcgi-4.4.9/bin/phpize ./configure –enable-apc –enable-apc-mmap –with-php-config=/opt/phpfcgi-4.4.9/bin/php-config make make install

Afterwards, open /opt/phpfcgi-4.4.9/lib/php.ini…

vi /opt/phpfcgi-4.4.9/lib/php.ini

… and set extension_dir = “/opt/phpfcgi-4.4.9/lib/php/extensions/no-debug-non-zts-20020429″ and add the line extension=apc.so at the end of the file (you can also configure some additional APC settings):

[...] extension_dir = "/opt/phpfcgi-4.4.9/lib/php/extensions/no-debug-non-zts-20020429" [...] extension=apc.so apc.enabled=1 apc.shm_segments=1 apc.shm_size=512 apc.ttl=0 apc.user_ttl=600 apc.gc_ttl=600 apc.enable_cli=1 apc.mmap_file_mask=/tmp/apc.XXXXXX ;apc.mmap_file_mask=/dev/zero ;apc.shm_segments = 5

In ISPConfig 3.0.5, you can configure the new PHP version under System > Additional PHP Versions. On the Name tab, you just fill in a name for the PHP version (e.g. PHP 4.4.9) – this PHP version will be listed under this name in the website settings in ISPConfig:

(JavaScript must be enabled in your browser to view the large image as an image overlay.)

Go to the FastCGI Settings tab (the PHP-FPM Settings tab can be left empty) and fill out the fields as follows:

(JavaScript must be enabled in your browser to view the large image as an image overlay.)

If everything is working as expected, you can now choose PHP 4.4.9 for a website in ISPConfig. You can check the PHP version of a website by creating a PHP file with the phpinfo(); function in it and calling that file in your browser:

(JavaScript must be enabled in your browser to view the large image as an image overlay.)

3 Links

About The Author

Falko Timme is the owner of Timme Hosting (ultra-fast nginx web hosting). He is the lead maintainer of HowtoForge (since 2005) and one of the core developers of ISPConfig (since 2000). He has also contributed to the O’Reilly book “Linux System Administration”.

New Post has been published on http://mocco.sk/tips-to-use-multiple-php-versions-php-fpm-fastcgi-with-ispconfig-3-ubuntu-12-04-lts/

Tips to Use Multiple PHP Versions (PHP-FPM & FastCGI) With ISPConfig 3 (Ubuntu 12.04 LTS)

Version 1.0 Author: Falko Timme <ft [at] falkotimme [dot] com> Follow me on Twitter Last edited 03/05/2013

Since ISPConfig 3.0.5, it is possible to use multiple PHP versions on one server and select the optimal PHP version for a website. This feature works with PHP-FPM (starting with PHP 5.3) and FastCGI (all PHP 5.x versions). This tutorial shows how to build PHP 5.3 and PHP 5.4 as a PHP-FPM and a FastCGI version on an Ubuntu 12.04 server. These PHP versions can be used together with the default PHP (installed through apt) in ISPConfig.

I do not issue any guarantee that this will work for you!

1 Preliminary Note

I will install PHP 5.3.22 and PHP 5.4.12, the latest PHP 5.3 and 5.4 versions at the time of this writing. I will also show how to build some additional PHP extensions such as APC, memcache, memcached, and ioncube.

Please note that PHP-FPM can be used on both Apache and nginx servers, while FastCGI is available only for Apache servers.

PHP-FPM and FastCGI are mutually exclusive in PHP 5.3 and 5.4, that’s why I show two ways of building PHP, one for PHP-FPM, one for FastCGI, however you can compile PHP twice to get both, one time with –enable-fpm and one time with –enable-cgi (make sure to use different base directories, such as /opt/php-5.3.22 for PHP-FPM and /opt/phpfcgi-5.3.22 for FastCGI).

2 Building PHP 5.3.22 (PHP-FPM)

Download and extract PHP 5.3.22:

mkdir /opt/php-5.3.22 mkdir /usr/local/src/php5-build cd /usr/local/src/php5-build wget http://de.php.net/get/php-5.3.22.tar.bz2/from/this/mirror -O php-5.3.22.tar.bz2 tar jxf php-5.3.22.tar.bz2

cd php-5.3.22/

Install the prerequisites for building PHP5:

apt-get install build-essential

apt-get build-dep php5

apt-get install libfcgi-dev libfcgi0ldbl libjpeg62-dbg libmcrypt-dev libssl-dev libc-client2007e libc-client2007e-dev

ln -s /usr/lib/libc-client.a /usr/lib/x86_64-linux-gnu/libc-client.a

(The last command is needed if you build PHP with –with-imap, because otherwise ./configure will stop with the following error:

checking for crypt in -lcrypt… yes configure: error: Cannot find imap library (libc-client.a). Please check your c-client installation. root@server1:/usr/local/src/php5-build/php-5.3.22#

)

Configure and build PHP 5.3.22 as follows (you can adjust the ./configure command to your needs, take a look at

./configure –help

to see all available options; if you use a different ./configure command, it is possible that additional libraries are required, or the build process will fail):

./configure \ –prefix=/opt/php-5.3.22 \ –with-pdo-pgsql \ –with-zlib-dir \ –with-freetype-dir \ –enable-mbstring \ –with-libxml-dir=/usr \ –enable-soap \ –enable-calendar \ –with-curl \ –with-mcrypt \ –with-zlib \ –with-gd \ –with-pgsql \ –disable-rpath \ –enable-inline-optimization \ –with-bz2 \ –with-zlib \ –enable-sockets \ –enable-sysvsem \ –enable-sysvshm \ –enable-pcntl \ –enable-mbregex \ –with-mhash \ –enable-zip \ –with-pcre-regex \ –with-mysql \ –with-pdo-mysql \ –with-mysqli \ –with-jpeg-dir=/usr \ –with-png-dir=/usr \ –enable-gd-native-ttf \ –with-openssl \ –with-fpm-user=www-data \ –with-fpm-group=www-data \ –with-libdir=/lib/x86_64-linux-gnu \ –enable-ftp \ –with-imap \ –with-imap-ssl \ –with-kerberos \ –with-gettext \ –enable-fpm

The last switch (–enable-fpm) makes sure this PHP version will work with PHP-FPM.

make make install

Copy php.ini and php-fpm.conf to the correct locations:

cp /usr/local/src/php5-build/php-5.3.22/php.ini-production /opt/php-5.3.22/lib/php.ini

cp /opt/php-5.3.22/etc/php-fpm.conf.default /opt/php-5.3.22/etc/php-fpm.conf

Open /opt/php-5.3.22/etc/php-fpm.conf and adjust the following settings – in the listen line you must use an unused port (e.g. 8999; port 9000 might be in use by Ubuntu’s default PHP-FPM already), and you must add the line include=/opt/php-5.3.22/etc/pool.d/*.conf at the end:

vi /opt/php-5.3.22/etc/php-fpm.conf

[...] pid = run/php-fpm.pid [...] user = www-data group = www-data [...] listen = 127.0.0.1:8999 [...] include=/opt/php-5.3.22/etc/pool.d/*.conf

Create the pool directory for PHP-FPM:

mkdir /opt/php-5.3.22/etc/pool.d

Next create an init script for PHP-FPM:

vi /etc/init.d/php-5.3.22-fpm

#! /bin/sh ### BEGIN INIT INFO # Provides: php-5.3.22-fpm # Required-Start: $all # Required-Stop: $all # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: starts php-5.3.22-fpm # Description: starts the PHP FastCGI Process Manager daemon ### END INIT INFO php_fpm_BIN=/opt/php-5.3.22/sbin/php-fpm php_fpm_CONF=/opt/php-5.3.22/etc/php-fpm.conf php_fpm_PID=/opt/php-5.3.22/var/run/php-fpm.pid php_opts="--fpm-config $php_fpm_CONF" wait_for_pid () { try=0 while test $try -lt 35 ; do case "$1" in 'created') if [ -f "$2" ] ; then try='' break fi ;; 'removed') if [ ! -f "$2" ] ; then try='' break fi ;; esac echo -n . try=`expr $try + 1` sleep 1 done } case "$1" in start) echo -n "Starting php-fpm " $php_fpm_BIN $php_opts if [ "$" != 0 ] ; then echo " failed" exit 1 fi wait_for_pid created $php_fpm_PID if [ -n "$try" ] ; then echo " failed" exit 1 else echo " done" fi ;; stop) echo -n "Gracefully shutting down php-fpm " if [ ! -r $php_fpm_PID ] ; then echo "warning, no pid file found - php-fpm is not running " exit 1 fi kill -QUIT `cat $php_fpm_PID` wait_for_pid removed $php_fpm_PID if [ -n "$try" ] ; then echo " failed. Use force-exit" exit 1 else echo " done" echo " done" fi ;; force-quit) echo -n "Terminating php-fpm " if [ ! -r $php_fpm_PID ] ; then echo "warning, no pid file found - php-fpm is not running " exit 1 fi kill -TERM `cat $php_fpm_PID` wait_for_pid removed $php_fpm_PID if [ -n "$try" ] ; then echo " failed" exit 1 else echo " done" fi ;; restart) $0 stop $0 start ;; reload) echo -n "Reload service php-fpm " if [ ! -r $php_fpm_PID ] ; then echo "warning, no pid file found - php-fpm is not running " exit 1 fi kill -USR2 `cat $php_fpm_PID` echo " done" ;; *) echo "Usage: $0 {start|stop|force-quit|restart|reload}" exit 1 ;; esac

Make the init script executable and create the system startup links:

chmod 755 /etc/init.d/php-5.3.22-fpm update-rc.d php-5.3.22-fpm defaults

Finally start PHP-FPM:

/etc/init.d/php-5.3.22-fpm start

As long as there are no pools in /opt/php-5.3.22/etc/pool.d, you will get this warning which you can ignore:

root@server1:/usr/local/src/php5-build/php-5.3.22# /etc/init.d/php-5.3.22-fpm start Starting php-fpm [04-Mar-2013 14:58:41] WARNING: Nothing matches the include pattern ‘/opt/php-5.3.22/etc/pool.d/*.conf’ from /opt/php-5.3.22/etc/php-fpm.conf at line 512. done root@server1:/usr/local/src/php5-build/php-5.3.22#

That’s it – if you like, you can now install some additional modules like APC, memcache, memcached, and ioncube.

The APC, memcache, and memcached modules can be installed through PEAR which we must install and initialize first:

apt-get -y install php-pear

cd /opt/php-5.3.22/etc

pecl -C ./pear.conf update-channels

APC can now be installed as follows:

pecl -C ./pear.conf install apc

Accept all default values. Afterwards, open /opt/php-5.3.22/lib/php.ini…

vi /opt/php-5.3.22/lib/php.ini

… and add the line extension=apc.so at the end of the file (you can also configure some additional APC settings):

[...] extension=apc.so apc.enabled=1 apc.shm_size=128M apc.ttl=0 apc.user_ttl=600 apc.gc_ttl=600 apc.enable_cli=1 apc.mmap_file_mask=/tmp/apc.XXXXXX ;apc.mmap_file_mask=/dev/zero ;apc.shm_segments = 5

The memcache extension can be installed as follows:

pecl -C ./pear.conf install memcache

Open /opt/php-5.3.22/lib/php.ini…

vi /opt/php-5.3.22/lib/php.ini

… and add the line extension=memcache.so at the end of the file:

[...] extension=memcache.so

The memcached extension can be installed as follows:

apt-get install libmemcached-dev

ln -s /usr/include/libmemcached /usr/include/libmemcached-1.0

pecl -C ./pear.conf install memcached

Open /opt/php-5.3.22/lib/php.ini…

vi /opt/php-5.3.22/lib/php.ini

… and add the line extension=memcached.so at the end of the file:

[...] extension=memcached.so

The ionCube Loader can be installed as follows:

cd /tmp

Next download and unpack the correct ionCube Loader package for your architecture (x86_64 or x86).

For x86_64:

wget http://downloads2.ioncube.com/loader_downloads/ioncube_loaders_lin_x86-64.tar.gz tar xfvz ioncube_loaders_lin_x86-64.tar.gz

For x86:

wget http://downloads2.ioncube.com/loader_downloads/ioncube_loaders_lin_x86.tar.gz tar xfvz ioncube_loaders_lin_x86.tar.gz

Proceed as follows:

cp ioncube/ioncube_loader_lin_5.3.so /opt/php-5.3.22/lib/php/extensions/no-debug-non-zts-20090626/ioncube.so vi /opt/php-5.3.22/lib/php.ini

Add the line zend_extension = /opt/php-5.3.22/lib/php/extensions/no-debug-non-zts-20090626/ioncube.so right at the beginning of the file (before the [PHP] line):

zend_extension = /opt/php-5.3.22/lib/php/extensions/no-debug-non-zts-20090626/ioncube.so [PHP] [...]

Reload PHP-FPM afterwards:

/etc/init.d/php-5.3.22-fpm reload

In ISPConfig 3.0.5, you can configure the new PHP version under System > Additional PHP Versions. On the Name tab, you just fill in a name for the PHP version (e.g. PHP 5.3.22) – this PHP version will be listed under this name in the website settings in ISPConfig:

(JavaScript must be enabled in your browser to view the large image as an image overlay.)

Go to the PHP-FPM Settings tab (the FastCGI Settings tab can be left empty) and fill out the fields as follows:

(JavaScript must be enabled in your browser to view the large image as an image overlay.)

How To Use Multiple PHP Versions (PHP-FPM & FastCGI) With ISPConfig 3 (Ubuntu 12.04 LTS) – Page 2