The location and organisation of the configuration files is configurable and can change between major releases or between distributions.
The Apache Wiki has a handy guide to the names and locations of the configuration files.
Because the config files can contain
include directives, parts of the configuration can be separated out into smaller files. Since a standard Apache configuration file contains many comments and lots of standard items, it makes some sense to separate out the parts you are most likely to change.
The name of the main configuration file can be changed at compilation time and in recent releases it has changed from
Over the years there has been some evolution in the organisation of the included configuration files too.
For example, I installed Apache2 on a Ubuntu-based system using
apt-get install apache2 - here's the included files
apache2.conf envvars mods-available ports.conf sites-enabled
conf.d httpd.conf mods-enabled sites-available
/etc/apache2$ grep ^Include apache2.conf
/etc/apache2$ ls -l sites-enabled
lrwxrwxrwx 1 root root 26 Dec 26 12:30 000-default -> ../sites-available/default
So the few configuration settings you are likely to be most interested in are now in
I can see that this is consistent with the Ubuntu documentation for Apache which I recommend you read first. If you have other documentation for older versions of Apache (or other distributions) you can adapt that information to suit the way things are organised in Ubuntu.