How To Set Up Apache2 With mod_fcgid And PHP5 On CentOS 6.2
|
Submitted by falko (Contact Author) (Forums) on Wed, 2012-05-23 17:51. :: CentOS | Web Server | Apache | PHP
How To Set Up Apache2 With mod_fcgid And PHP5 On CentOS 6.2Version 1.0 This tutorial describes how you can install Apache2 with mod_fcgid and PHP5 on CentOS 6.2. mod_fcgid is a compatible alternative to the older mod_fastcgi. It lets you execute PHP scripts with the permissions of their owners instead of the Apache user. I do not issue any guarantee that this will work for you!
1 Preliminary NoteI'm using a CentOS 6.2 server in this tutorial with the hostname server1.example.com and the IP address 192.168.0.100. I will create two Apache vhosts in this tutorial, www.example1.com and www.example2.com, to demonstrate the usage of mod_fcgid. Before we start, make sure that SELinux is disabled. Edit /etc/selinux/config and set SELINUX=disabled: vi /etc/selinux/config
Afterwards we must reboot the system: reboot
2 Installing Apache2/mod_fcgi/PHP5mod_fcgid is not available in the official CentOS repositories, but there's a package in the EPEL repository. We enable the repository as follows: rpm --import https://fedoraproject.org/static/0608B895.txt yum install yum-priorities Edit /etc/yum.repos.d/epel.repo... vi /etc/yum.repos.d/epel.repo ... and add the line priority=10 to the [epel] section:
Afterwards we can install Apache2, mod_fcgid, and PHP5: yum install httpd mod_fcgid php-cli If Apache2 was already installed with PHP5 as an Apache module, disable the PHP5 module now - open /etc/httpd/conf.d/php.conf... vi /etc/httpd/conf.d/php.conf ... and comment out everything in that file:
Then we create the system startup links for Apache and start it: chkconfig --levels 235 httpd on Next we open /etc/php.ini... vi /etc/php.ini ... and uncomment the line cgi.fix_pathinfo=1:
Open /etc/httpd/conf.d/fcgid.conf... vi /etc/httpd/conf.d/fcgid.conf ... and add the line PHP_Fix_Pathinfo_Enable 1 at the end:
Then reload Apache: /etc/init.d/httpd reload
3 Creating Vhosts For www.example1.com And www.example2.comI will now create two vhosts, www.example1.com (with the document root /var/www/web1/web) and www.example2.com (with the document root /var/www/web2/web). www.example1.com will be owned by the user and group web1, and www.example2.com by the user and group web2. First we create the users and groups: groupadd web1 Then we create the document roots and make them owned by the users/groups web1 resp. web2: mkdir -p /var/www/web1/web We will run PHP using suExec; suExec's document root is /var/www, as the following command shows: /usr/sbin/suexec -V [root@server1 ~]# /usr/sbin/suexec -V Therefore we cannot call the PHP binary (/usr/bin/php-cgi) directly because it is located outside suExec's document root. As suExec does not allow symlinks, the only way to solve the problem is to create a wrapper script for each web site in a subdirectory of /var/www; the wrapper script will then call the PHP binary /usr/bin/php-cgi. The wrapper script must be owned by the user and group of each web site, therefore we need one wrapper script for each web site. I'm going to create the wrapper scripts in subdirectories of /var/www/php-fcgi-scripts, e.g. /var/www/php-fcgi-scripts/web1 and /var/www/php-fcgi-scripts/web2. mkdir -p /var/www/php-fcgi-scripts/web1 vi /var/www/php-fcgi-scripts/web1/php-fcgi-starter
vi /var/www/php-fcgi-scripts/web2/php-fcgi-starter
The PHPRC line contains the directory where the php.ini file is located (i.e., /etc/ translates to /etc/php.ini). PHP_FCGI_MAX_REQUESTS is the maximum number of requests before an fcgid process is stopped and a new one is launched. PHP_FCGI_CHILDREN defines the number of PHP children that will be launched. The php-fcgi-starter scripts must be executable, and they (and the directories they are in) must be owned by the web site's user and group: chmod 755 /var/www/php-fcgi-scripts/web1/php-fcgi-starter Now we create the Apache vhosts for www.example1.com and www.example2.com. Add the following two vhosts at the end of /etc/httpd/conf/httpd.conf: vi /etc/httpd/conf/httpd.conf
Make sure you fill in the right paths (and the correct user and group in the SuexecUserGroup lines). Reload Apache afterwards: /etc/init.d/httpd reload
|




Recent comments
11 hours 8 min ago
16 hours 13 min ago
20 hours 37 min ago
22 hours 26 min ago
1 day 12 hours ago
1 day 12 hours ago
1 day 17 hours ago
2 days 22 min ago
2 days 1 hour ago
2 days 2 hours ago