On 9/19/07, Steve Potter <[EMAIL PROTECTED]> wrote: > > I currently have a dedicated server running a Cpanel installation with > several virtual hosts. I would like to install Django on this server > and as far as I can tell, I have several options. > > 1. Add mod_python to existing Apache installation > 2. Add FastCGI to existing Apache installation > 3. Install secondary server (another installation of apache lighttpd, > etc..) bound to another ip address for Django > 4. Same as above, but instead of a different ip address use localhost > and install mod_proxy on existing Apache. > 5. Use a different server.
Unless you are on what cPanel calls the bleeding edge, you're running Apache 1.3 which is useless for serving Django. That leaves you with either #3 or #4. #3 has issues because cPanel wants to bind Apache to all IP addresses. I had issues (though I didn't troubleshoot them throuroughly) with changing httpd.conf to only attach to specific IPs. #4 is inefficient and a pain to maintain. I'm moving all my Django apps to Slicehost because the cPanel setup is so ugly. If you do go this route, I'd highly recommend using daemontools to manage your django FCGI processes. It has served me well. You may also find this helpful http://coderseye.com/2007/lighttpd-on-cpanel-vps.html --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
