CentOS 6.4 and PHP 5.3
In the first article, I described how I set up CentOS 6.4 including with Apache to get ready for web development. In this article, I’ll describe what I did to get CentOS and PHP 5.3 up and running.
First, you’ve read the first article right?
The next thing we’ll do is add PHP 5.3 into the mix.
It seems that most of what we need is available is available from here:
Do a search for PHP, and you’ll find plenty of PHP 5.3 options to choose from. Here are the main components I installed:
I also added these:
And finally, we’ll add Xdebug:
Then it’s just a question of clicking “Apply” and letting CentOS sort out the dependencies for you.
Next, open up Terminal, and restart Apache:
sudo service httpd restart
Then, you can create a PHP file in your
public_html folder called
info.php. Add this code:
Save it, and then we can try it out in the browser:
PHP 5.3 Short Tags
I use CodeIgniter quite a lot. And in views I like to use the short tag:
. It’s switched off by default though, but we can fix that.
Drop back into Terminal and do:
sudo gedit /etc/php.ini
Then, on around line 229 change it from
On. Save and close the file, then restart Apache:
sudo service httpd restart.
Add a Repository
You’ll need to add a repository to make stuff like phpMyAdmin available in Add/Remove software. The link to the repository can be found here.
To add it, drop back into Terminal an do:
rpm -Uvh http://download.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm
You’ll find this available in “Add/Remove Software” too. Again, CentOS will resolve the dependencies for you.
MySQL is already installed, so drop back into Terminal, and start the server:
sudo service mysqld start
You’ll be prompted to change the root password, which you should:
usr/bin/mysqladmin -u root password 'new-password'
Then you can access phpMyAdmin at:
We’ve installed PHP and supporting libraries, we’ve added phpMyAdmin, and changed the MySQL root password. Next, we’ll get Ruby and Rails installed.
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)