Ubuntu Hardy - Apache Configuration Layout
Ubuntu Hardy Heron uses a different Apache layout than you may have encountered if you have used Apache with non-Debian based Operating Systems.
The differences are not huge and, indeed, help in configuring and deploying websites.
Assuming you have used aptitude to install Apache (see the Ubuntu Hardy - Apache and PHP install install article), move into the config folder and have a look:
cd /etc/apache2 ls
You will see this:
The folders are highlighted in blue. Let's look at those first:
Inside sites-available will be files containing the configurations for each site you want to serve - these are known as vhosts or virtual hosts.
Have a look now and see that there is one site (default) available:
ls sites-available/ ... default
The apache install has a 'default' vhost available - when we navigated to the Cloud Server IP and got the 'It works!" message, it was this default file that told Apache what to do and where the files where located.
We'll look at vhosts in more detail and create our own in a later article.
Do note that a file in sites-available does not mean they are active. They are simply available for serving if you enable them. Which brings us to...
This folder contains symlinks to the sites you actually want to serve.
For example, you could have 2 vhosts configured and ready to use in the sites-available folder, but only one of them enabled. Only the one symlinked from the sites-enabled folder would be served.
Have a look at the default contents:
ls -l sites-enabled ... lrwxrwxrwx 1 root root 36 Apr 28 10:40 000-default -> /etc/apache2/sites-available/default
This means that the 'default' site has been enabled - the symlink named '000-default' links to the 'default' file in the sites-available folder.
Without the symlink in this folder it would remain available (in the sites-available folder) but not active.
The other thing to note is the naming. It's possible for a domain to point to your Cloud Server IP but have no site configuration file. In these cases, the first enabled site (alphabetically) will be displayed i.e. 000-default's config will be used.
Well, I guess you get the idea already but this folder holds the modules that are available to be loaded.
Have a look:
A fair list is available from our base install but remember that they are not all enabled, merely available for use.
Just as with the vhosts files, any modules that we want to use must be enabled.....
This folder contains symlinks to the modules that we want enabled. Have a look and compare it to the list of modules available:
This list is a lot shorter than the list of available modules (meaning not all the available modules are enabled) and includes php5.conf - which is handy as we installed PHP5 earlier.
a2en and a2dis
Being a good sysadmin, we like to get stuck in and create our vhosts and now we know how the symlinks work we could go ahead and 'ln -s' until all our sites are enabled.
However, there are some commands that make this process much easier.
They are a2dissite, a2ensite, a2dismod and a2enmod.
This will delete the symlink to a site you have previously enabled.
For example, let's disable the default site:
sudo a2dissite default
The symlink in sites-enabled has been deleted and the output is as follows:
Site default disabled; run /etc/init.d/apache2 reload to fully disable.
Reload Apache as indicated to ensure the site is fully disabled:
sudo /etc/init.d/apache2 reload
When you now visit your Cloud Server IP, instead of the nice 'It Works!' page, you will get a 404 Not Found message.
Note the main vhosts file in sites-available is still there - all the a2dissite command did was remove the symlink in the sites-enabled folder.
Let's enable the default site again:
sudo a2ensite default
Site default installed; run /etc/init.d/apache2 reload to enable.
sudo /etc/init.d/apache2 reload
Visit your Cloud Server IP - the default 'It works!' page is being served again.
In the same way as just shown, a2dismod will disable any modules you have previously enabled:
sudo a2dismod php5
Module php5 disabled; run /etc/init.d/apache2 force-reload to fully disable.
That will disable the php5 module and if you look in the mods-enabled folder, you will see that the symlinks php5.conf and php5.load have been deleted.
I reckon you've got it now, but to enable the php5 module simply enter:
sudo a2enmod php5
Module php5 installed; run /etc/init.d/apache2 force-reload to enable.
And a quick check will show that indeed, the php5.conf and php5.load symlinks are back in the mods-enabled folder.
Don't forget to reload Apache after each site or module change.
The next couple of articles will discuss the main apache2.conf file and look at what changes can be made to optimize the install.
© 2011-2013 Rackspace US, Inc.
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License
See license specifics and DISCLAIMER