These instructions have not been updated for Debian Squeeze. The process is probably easier now, and this page should be updated.
1. Serving Django
Running your own Apache, mod_wsgi and Django on HCOOP is reasonable easy. You must realize that you're not doing a server installation, but a local (aka your own home-directory) installation. Apache don't care, as long as you enter the correct configuration.
The only tricky part is Virtualenv. You need this popular Python tool to create a your own Django environment. Using Virtualenv is straight forward. Unfortunaly, Virtualenv makes the installation and configuration of your other tools a little bit more complex. Therefore, I created this page to help you through these steps.
1.1. Apache http server
Download the latest version from http://apache.org. Choose for unix source and build your Apache yourself. If you follow the instructions, then it is quite simple. Don't forget to include the mod_rewrite module in your build. Also, don't do /apache which you're not allowed on HCOOP, but $HOME/apache. Also, notice that I use $HOME. For some reason ~/apache doesn't work with configure but $HOME works fine.
./configure --prefix=$HOME/sw/pkg/apache --enable-rewrite make make install
More information is on RunningYourOwnApache.
Just download the source, follow the instructions and you'll be fine. The documentation emphasize that use the same python version for compiling, as well as running. This is a good reason to overwrite the defaults and point to the python that you want. I want version 2.5 in a Virtualenv environment. $YOURVIRTUALENV/bin/python is a 2.5 interpreter. Notice that I will use this environment for compiling mod_wsgi, as well as running mod_wsgi with the proper instructions in httpd.conf.
./configure --with-apxs=$HOME/$YOURAPACHE/bin/apxs --with-python=$HOME/$YOURVIRTUALENV/bin/python make make install
1.3.2. Static media
You need to organize a couple of things in the Apache configuration file. First of all, you want an alias for your "favicon.ico". With a static web-site the favicon is in the document root. I prefer the favicon in the same directory as my other static media. Therefore you need an alias for the directory with your static media, as well as an alias for your favicon. Don't forget to add the Directory entry for this directory.
For the Admin part of your Django project you will probably use the default Django admin pages and media files. Add a symbolic link to your Django directory (don't forget to add followsymlinks to your Apache configuration) and configure that one too.
1 alias /media/ /$YOURPROJECT/media/
1.3.3. WSGI & Django
1 WSGIPythonHome /afs/hcoop.net/user/n/na/nachtdier/$YOURVIRTUALENV 2 3 Alias /favicon.ico /afs/hcoop.net/user/n/na/nachtdier/$YOURDJANGO/site_media/img/favicon.ico 4 Alias /site_media/ /afs/hcoop.net/user/n/na/nachtdier/$YOURDJANGO/site_media/ 5 6 <Directory /afs/hcoop.net/user/n/na/nachtdier/$YOURDJANGO/site_media> 7 Order allow,deny 8 Allow from all 9 </Directory> 10 11 Alias /media/ /afs/hcoop.net/user/n/na/nachtdier/$YOURDJANGO/media/ 12 13 <Directory /afs/hcoop.net/user/n/na/nachtdier/$YOURDJANGO/media> 14 Order allow,deny 15 Allow from all 16 </Directory> 17 18 WSGIScriptAlias / /afs/hcoop.net/user/n/na/nachtdier/$YOURDJANGO/apache/django.wsgi 19 20 <Directory /afs/hcoop.net/user/n/na/nachtdier/$YOURDJANGO/apache> 21 Order allow,deny 22 Allow from all 23 </Directory>
On HCOOP, one should not use the normal Unix autorisation, but AFS instead. RunningYourOwnApache describes the necessary part for Apache (e.g. k5start). You must do the part of your application yourself. Notice that the autorisation is for USER.daemon instead of USER.
So far, I've found that one must set the proper autorisation for Apache itself, your virtualenv directory with Python and your Django directory. My current setup is the same autorisation for USER.daemon for all directories. Feel free to suggest a more specific setup on this page.
fsr setacl $YOURAPACHE nachtdier.daemon all fsr setacl $YOURVIRTUALENV nachtdier.daemon all fsr setacl $YOURDJANGO nachtdier.daemon all
2. Configuring Django
You need to have a special WSGI script in your Django project. Don't put this one in the same directory as your settings file but use a subdirectory. Only then you can enter a separate Directory with the appropriate allow and deny. You don't want to expose your directory with your settings file.
It is very important to understand that an unattended, production Apache is really something different from ./manage.py runserver. For example, you must use an absolute path for the location of your SQLite database instead of the more familiar "django.db". Fortunaly, the Apache error_log shows this type of errors.
3. Other information
3.1. Simple test
For simple test installations, it's easy: Django for Python2.5 is already installed, and (unless some new firewall is in place,) you can open high ports and access them from abroad via ip address (use /sbin/ifconfig eth0 to identify IP address.)
Django's webserver can be seen with:
python manage.py runserver 0.0.0.0:8024
Virtualenv is not available in the python installation on HCOOP. You must download (wget) the script yourself and put it somewhere under your home directory.
The environment that you create does include PIP. PIP is the new and improved easy_install. The option "freeze" works great with HCOOP. Create your Python environment (including Django ofcourse) on your home PC. Create the requirement file with 'pip freeze > yourrequirements.txt'. Push that file to HCOOP. Go to the bin directory in your environment. Use 'pip install -r yourrequirements.txt' and automatically everything is installed in that environment.
Virtualenv uses the default python interpreter for the virtual environment. On HCOOP the default is version 2.4. Support for SQLite is included in 2.5, so I prefer that version for Django. Python 2.5 is also available on HCOOP. Use the parameter -p python2.5 and that version will be installed in your environment. Don't forgot to use that version for mod_wsgi too.
1 ./virtualenv.py -p python2.5 --no-site-packages $YOURVIRTUALENV
The application CherryPy is also very good in serving Python applications. CherryPy is also a Web Framework, but you can use it for serving only. The Django application cpserver integrates CherryPy nicely in Django with Django commands. It did run great at home and HCOOP. Unfortunaly I was never able to integrate it with the mod_rewrite in the Domtool. I'm quite sure it was my shortcoming. I solved the issue with a switch to mod_wsgi.