Django issues (or issues with Django)
My initial exuberance with Django has been tempered a bit by trying to get it to run on a production server. Getting Rails to run was a snap compared to getting Django to run on a Plesk server.
Once I realized I had to install an earlier version of mod-python (3.1.4) and finally got it running I was confronted with the “The Dreaded Segmentation Fault” which crashed Apache.
Patching expat as described in the article was easy enough but I still had trouble running any pages that accessed the database. So I might have had both install issues at the bottom of the Django deployment page. Even when serving up non-dynamic pages the server resources where going throught the roof.
It seems mod_python and PHP just don’t want to play nice together, and there’s now way I can give uninstall PHP too many of our old sites use it. Maybe running Django under FastCGI is the way to go.
Like this post? subscribe to the feed.
I know this post was nearly two years ago but did you find a good way to run Django on a Plesk box (even if you had to remove PHP)? I’m running only Django on my box so the PHP aspect won’t really matter.
Comment by Brian — April 23, 2008 @ 7:39 am
Hey Brian,
I didn’t get this solved under Plesk as I always needed PHP, my solution was to grab a SliceHost server and only install Python/MySQL/Django on it then use some DNS/mod rewrite trickery to have the dynamic stuff handled by Django/Slichost and the static stuff by Plesk.
P.S. Media Temple will have a Django container on their (gs) plans soon.
http://www.mediatemple.net/labs/grid/gc-django-beta.htm
Comment by Alastair — April 23, 2008 @ 7:20 pm