If you've followed the previous article you should have Apache and mod_wsgi ready to serve an app for you.
In this article we'll create a basic Django app and setup the virtual host that will allow Apache and mod_wsgi to work their magic.
First thing's first, move to your home directory and go into your public_html/domain1.com folder (if you don't have one, create one and of course give it the name of your domain rather than domain1.com):
Next you'll want to create a Django project which is done with the django-admin.py tool:
django-admin.py startproject testproject
For Apache to be able to actually serve a Django application it needs to know that it should hand off certain requests to mod_wsgi. We also need to create a WSGI file to tell mod_wsgi how to handle our requests. To accomplish this, we'll setup a virtual host that tells Apache where our WSGI file is and then setup the WSGI file accordingly.
This example is very basic but it will get you going:
sudo nano /etc/apache2/sites-available/domain1.com
Then type or copy the following virtual host definition:
ServerName domain1.com ServerAlias www.domain1.com WSGIScriptAlias / /home/demo/public_html/domain1.com/testproject.wsgi
This tells Apache to pass any request it receives to mod_wsgi and to use the WSGI file we specified earlier. Now to create the WSGI file:
Then add the following WSGI definition:
import os import sys sys.path.append('/home/demo/public_html/domain1.com/') os.environ['DJANGO_SETTINGS_MODULE'] = 'testproject.settings' import django.core.handlers.wsgi application = django.core.handlers.wsgi.WSGIHandler()
This will take care of importing the necessary modules, append our Django project path to the Python path and set a few variables to help mod_wsgi do its job. Once completed, you'll need to enable the virtual host and reload Apache:
sudo a2ensite domain1.com sudo /etc/init.d/apache2 reload
Providing everything went as expected you should be able to visit your domain (or slice IP) in your browser and get your newly created Django application. It should look something like this:
Note: If you get any port and NameVirtualHost errors upon reloading Apache, please ensure you read the Apache Virtual Hosts article.
As the astute of you may have noticed, there is one caveat to the virtual host definition provided in that it does not allow the serving of static content.
That is to say, no document root was specified and there is nothing to indicate that static files are not to be handled by mod_wsgi and Django.
The Django team actually recommends you use a secondary web server to serve static content, however, you can make a few tweaks in your testproject/settings.py file and use the following virtual host definition:
ServerName domain1.com ServerAlias www.domain1.com WSGIScriptAlias / /home/demo/public_html/domain1.com/testproject.wsgi Alias /static/ /home/demo/public_html/domain1.com/static/ <Location "/static/"> Options -Indexes
The Alias directive tells Apache to not let Django/mod_wsgi handle anything that's located under /static/ on your site. You can set this to be anything you like, but you'll need to make the appropriate directory available under /home/demo/public_html/domain1.com. In this example the directory would be called "static".
Tweaks for the settings.py file involve setting the MEDIA_URL and MEDIA_ROOT settings appropriately:
Find the following two settings and edit them like so:
MEDIA_ROOT = '/home/demo/public_html/domain1.com/static/' MEDIA_URL = '/static/'
Restart Apache now to make the updates take effect:
sudo /etc/init.d/apache2 reload
Now any items placed in /home/demo/public_html/domain1.com/static can be accessed via http://domain1.com/static/path/to/file.
When you update your python code or templates in a Django application with mod_wsgi, you must give Apache a reload to see the changes. So it's good to get into the habit of reloading Apache after making any changes to your project.
At this point you should now be able to successfully build out a Django application and have mod_wsgi as well as Apache serve it up for you.
© 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