LAMP Server on Ubuntu 9.10 (Karmic)
- Ubuntu 22.04
- Ubuntu 20.04
- Ubuntu 18.04
- Debian 8
- Debian 10
- CentOS 8
- CentOS 7
- Arch Linux
- Deprecated guides:
- Ubuntu 9.04
- Ubuntu 8.04
- Ubuntu 16.04
- Ubuntu 14.04
- Ubuntu 12.04
- Ubuntu 11.10
- Ubuntu 11.04
- Ubuntu 10.10
- Fedora 20
- Fedora 19
- Fedora 15
- Fedora 14
- Fedora 13
- Fedora 12
- Fedora 11
- Debian 7
- Debian 6
- Debian 5
- CentOS 6
- CentOS 5
Traducciones al EspañolEstamos traduciendo nuestros guías y tutoriales al Español. Es posible que usted esté viendo una traducción generada automáticamente. Estamos trabajando con traductores profesionales para verificar las traducciones de nuestro sitio web. Este proyecto es un trabajo en curso.
This guide has been deprecated and is no longer being maintained.
This guide provides step by step instructions for installing a full featured LAMP stack on an Ubuntu 9.10 (Karmic) system. You will be instructed on setting up Apache, MySQL, and PHP. If you don’t feel that you will need MySQL or PHP, please don’t feel obligated to install them.
It is important to make sure that your system is properly configured before installing Apache. In particular, you need to make sure that your system is up to date and that you have set the correct timezone, hostname, and hosts in your hosts file. If you haven’t configured these, you should follow the directions in the Setting Up and Securing a Compute Instance. This guide assumes that you are logged in as the root superuser on your Linode.
Install and Configure the Apache Web Server
The Apache Web Server is a very popular choice for serving web pages. While many alternatives have appeared in the last few years, Apache remains a powerful option that we recommend for most uses.
Make sure your package repositories and installed programs are up to date by issuing the following commands:
apt-get update apt-get upgrade --show-upgraded
To install the current version of the Apache web server (in the 2.x series) on an Ubuntu system use the following command:
apt-get install apache2
Now we’ll configure virtual hosting so that we can host multiple domains (or subdomains) with the server. These websites can be controlled by different users, or by a single user, as you prefer.
Configure Virtual Hosting
There are different ways to set up Virtual Hosts, however we recommend the method below.
By default, Apache listens on all IP addresses available to it. We must configure it to listen only on addresses we specify. Even if you only have one IP, it is still a good idea to tell Apache what IP address to listen on in case you decide to add more.
Begin by modifying the
NameVirtualHost entry in
/etc/apache2/ports.conf as follows:
- File: /etc/apache2/ports.conf
Be sure to replace “184.108.40.206” with your Linode’s public IP address.
Now, modify the default site’s virtual hosting in the file
/etc/apache2/sites-available/default so that the
<VirtualHost > entry reads:
- File: /etc/apache2/sites-available/default
Configure Name-based Virtual Hosts
First, create a file in the
/etc/apache2/sites-available/ directory for each virtual host that you want to set up. Name each file with the domain for which you want to provide virtual hosting. See the following example configurations for the hypothetical “example.com” and “example.org” domains.
- File: /etc/apache2/sites-available/example.com
1 2 3 4 5 6 7 8
<VirtualHost 220.127.116.11:80> ServerAdmin email@example.com ServerName example.com ServerAlias www.example.com DocumentRoot /srv/www/example.com/public_html/ ErrorLog /srv/www/example.com/logs/error.log CustomLog /srv/www/example.com/logs/access.log combined </VirtualHost>
- File: /etc/apache2/sites-available/example.org
1 2 3 4 5 6 7 8
<VirtualHost 18.104.22.168:80> ServerAdmin firstname.lastname@example.org ServerName example.org ServerAlias www.example.org DocumentRoot /srv/www/example.org/public_html/ ErrorLog /srv/www/example.org/logs/error.log CustomLog /srv/www/example.org/logs/access.log combined </VirtualHost>
Notes regarding this example configuration:
- All of the files for the sites that you host will be located in directories that exist underneath
/srv/wwwYou can symbolically link these directories into other locations if you need them to exist in other places.
CustomLogentries are suggested for more fine-grained logging, but are not required. If they are defined (as shown above), the
logsdirectories must be created before you restart Apache.
Before you can use the above configuration you’ll need to create the specified directories. For the above configuration, you can do this with the following commands:
mkdir -p /srv/www/example.com/public_html mkdir /srv/www/example.com/logs mkdir -p /srv/www/example.org/public_html mkdir /srv/www/example.org/logs
After you’ve set up your virtual hosts, issue the following commands:
a2ensite example.com a2ensite example.org
This command symbolically links your virtual host file from
sites-available to the
sites-enabled directory. Finally, before you can access your sites you must reload Apache with the following command:
Assuming that you have configured the DNS for your domain to point to your Linode’s IP address, Virtual hosting for your domain should now work.
If you wanted to disable the
example.com site, for example issue the following command:
a2dissite command is the inverse of
a2ensite. After enabling, disabling, or modifying any part of your Apache configuration you will need to reload the Apache configuration again with the
/etc/init.d/apache2 reload command. You can create as many virtual hosting files as you need to support the domains that you want to host with your Linode.
Install and Configure MySQL Database Server
MySQL is a relational database management system (RDBMS) and is a popular component in contemporary web development tool-chains. It is used to store data for many popular applications, including WordPress and Drupal.
The first step is to install the mysql-server package, which is accomplished by the following command:
apt-get install mysql-server
During the installation you will be prompted for a password. Choose something secure (use letters, numbers, and non-alphanumeric characters) and record it for future reference.
At this point MySQL should be ready to configure and run. While you shouldn’t need to change the configuration file, note that it is located at
/etc/mysql/my.cnf for future reference.
Configure MySQL and Set Up MySQL Databases
After installing MySQL, it’s recommended that you run
mysql_secure_installation, a program that helps secure MySQL. While running
mysql_secure_installation, you will be presented with the opportunity to change the MySQL root password, remove anonymous user accounts, disable root logins outside of localhost, and remove test databases. It is recommended that you answer yes to these options. If you are prompted to reload the privilege tables, select yes. Run the following command to execute the program:
Next, we’ll create a database and grant your users permissions to use databases. First, log in to MySQL:
mysql -u root -p
Enter MySQL’s root password, and you’ll be presented with a MySQL prompt where you can issue SQL statements to interact with the database.
To create a database and grant your users permissions on it, issue the following command. Note, the semi-colons (
;) at the end of the lines are crucial for ending the commands. Your command should look like this:
create database webdata; grant all on webdata.* to 'username' identified by 'password';
In the example above,
webdata is the name of the database,
username is the username, and
password password. Note that database user names and passwords are only used by scripts connecting to the database, and that database user account names need not (and perhaps should not) represent actual user accounts on the system.
With that completed you’ve successfully configured MySQL and you may now pass these database credentials on to your users. To exit the MySQL database administration utility issue the following command:
With Apache and MySQL installed you are now ready to move on to installing PHP to provide scripting support for your web pages.
Installing and Configuring PHP
PHP makes it possible to produce dynamic and interactive pages using your own scripts and popular web development frameworks. Furthermore, many popular web applications like WordPress are written in PHP. If you want to be able to develop your websites using PHP, you must first install it.
Ubuntu includes packages for installing PHP from the terminal. Issue the following command:
apt-get install php5 php-pear
Once PHP5 is installed we’ll need to tune the configuration file located in
/etc/php5/apache2/php.ini to enable more descriptive errors, logging, and better performance. These modifications provide a good starting point if you’re unfamiliar with PHP configuration.
Make sure that the following values are set, and relevant lines are uncommented (comments are lines beginning with a semi-colon (
- File: /etc/php5/apache2/php.ini
1 2 3 4 5 6 7
max_execution_time = 30 memory_limit = 64M error_reporting = E_COMPILE_ERROR|E_RECOVERABLE_ERROR|E_ERROR|E_CORE_ERROR display_errors = Off log_errors = On error_log = /var/log/php.log register_globals = Off
If you need support for MySQL in PHP, then you must install the php5-mysql package with the following command:
apt-get install php5-mysql
To install the php5-suhosin package, which provides additional security for PHP 5 applications (recommended), you must add the “universe” software repositories. Uncomment the following lines from
- File: /etc/apt/sources.list
1 2 3 4 5 6 7
deb http://us.archive.ubuntu.com/ubuntu/ karmic universe deb-src http://us.archive.ubuntu.com/ubuntu/ karmic universe deb http://us.archive.ubuntu.com/ubuntu/ karmic-updates universe deb-src http://us.archive.ubuntu.com/ubuntu/ karmic-updates universe deb http://security.ubuntu.com/ubuntu karmic-security universe deb-src http://security.ubuntu.com/ubuntu karmic-security universe
Now run the following command to update the package archive:
Install the suhosin package by issuing:
apt-get install php5-suhosin
Finally, restart Apache to make sure everything is loaded correctly:
You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.
This page was originally published on