Q:

Can Django be configured without httpd.conf modifications?

So I had someone working with me who setup the server functionality of the Django site. It is working great directly on the IP in the browser. So we just finished building the site, and want to hook up the domain.
I checked /etc/httpd/conf/httpd.conf and that file has nothing related to the Django site. I've setup a few Django sites in the past, but I have always used httpd.conf. 
Where could he have possibly set up the WSGI?
Version details:
CentOS release 6.6 (Final)
Apache server version: Apache/2.2.15
Python 2.7.9 (via Virtual Env) with Django 1.6.0

A:

On Linux systems, additions for specific sites are generally never stuck in the httpd.conf file. Instead they would be in separate files for each site under a sites-available directory, which in turn would be symlinked into a sites-enabled directory. The main Apache configuration files would then use the Include directive to include all files from the sites-enabled directory.

