Comments on: Setup mod_wsgi for Django and Shared Hosting http://www.davidcramer.net/code/django/108/setup-mod_wsgi-for-django-and-shared-hosting.html A blog about Django, JavaScript, CSS, and general web development. Wed, 20 Aug 2008 16:04:49 +0000 http://wordpress.org/?v=2.6 By: jobscry http://www.davidcramer.net/code/django/108/setup-mod_wsgi-for-django-and-shared-hosting.html#comment-19893 jobscry Sun, 01 Jun 2008 01:01:03 +0000 http://www.davidcramer.net/code/django/108/setup-mod_wsgi-for-django-and-shared-hosting.html#comment-19893 dude, you rock. good info. had some problem with the admin media but turned out to be a permissions error. dude, you rock. good info. had some problem with the admin media but turned out to be a permissions error.

]]> By: David http://www.davidcramer.net/code/django/108/setup-mod_wsgi-for-django-and-shared-hosting.html#comment-19584 David Tue, 25 Mar 2008 18:15:08 +0000 http://www.davidcramer.net/code/django/108/setup-mod_wsgi-for-django-and-shared-hosting.html#comment-19584 Arne, sounds like your method would work great for hosting multiple projects under the same domain. Arne, sounds like your method would work great for hosting multiple projects under the same domain.

]]> By: Arne Brodowski http://www.davidcramer.net/code/django/108/setup-mod_wsgi-for-django-and-shared-hosting.html#comment-19558 Arne Brodowski Mon, 24 Mar 2008 14:59:25 +0000 http://www.davidcramer.net/code/django/108/setup-mod_wsgi-for-django-and-shared-hosting.html#comment-19558 I use a combination of mod_wsgi and mod_vhost_alias to reduce apache config changes to a minimum for each new site. Per-site configuration (except for WSGIDaemonProcess directives) are written in a .htaccess file. I've documented the setup here (in german, but the listings should be readable) http://django-hosting.de/wiki/ApacheModWsgi/ I use a combination of mod_wsgi and mod_vhost_alias to reduce apache config changes to a minimum for each new site.
Per-site configuration (except for WSGIDaemonProcess directives) are written in a .htaccess file.

I’ve documented the setup here (in german, but the listings should be readable) http://django-hosting.de/wiki/ApacheModWsgi/

]]> By: David http://www.davidcramer.net/code/django/108/setup-mod_wsgi-for-django-and-shared-hosting.html#comment-19534 David Sun, 23 Mar 2008 21:49:10 +0000 http://www.davidcramer.net/code/django/108/setup-mod_wsgi-for-django-and-shared-hosting.html#comment-19534 Thanks for the reply Graham. I'll be changing the process count and the process name for sure :) Thanks for the reply Graham. I’ll be changing the process count and the process name for sure :)

]]> By: Graham Dumpleton http://www.davidcramer.net/code/django/108/setup-mod_wsgi-for-django-and-shared-hosting.html#comment-19529 Graham Dumpleton Sun, 23 Mar 2008 09:25:44 +0000 http://www.davidcramer.net/code/django/108/setup-mod_wsgi-for-django-and-shared-hosting.html#comment-19529 It is best not to include 'processes=1' option to WSGIDaemonProcess but let it apply its default of 1. This is because there is a subtle little difference between each. When it defaults to 1, wsgi.multiprocess is False, where as setting 'processes=1' results in wsgi.multiprocess is True. This distinction exists for where one may use a means of mapping across multiple process groups in same server, or requests are handled across multiple servers in a cluster. In other words, one needs a way of saying the application is logically hosted in a multiprocess setup even though only one process in that particular process group. I know it may be a bit non obvious, but best I could could up with at the time. Where does this matter? It matters if you want to use an in browser application debugger such as Paste EvalException or the one from Werkzeug. This will not work in a multiprocess setup as it relies on requests going back to the same process. In your setup the requests will go back to the same process, but debuggers such as EvalException think it is multiprocess setup and will not allow you to run it. So check out the ConfigurationDirectives document on mod_wsgi wiki as well as the DebuggingTechniques document. BTW, you might also look at the display-name option for WSGIDaemonProcess for mod_wsgi 2.0. Use that and 'ps' can be used to distinguish each users processes rather than them all appearing as being named 'httpd'. Finally, you might also look at VirtualEnvironments document on wiki and setup things so that each user is working out of a Python virtual environment constructed using 'virtualenv'. That way it is a lot easier for them to install their own Python packages. It is best not to include ‘processes=1′ option to WSGIDaemonProcess but let it apply its default of 1. This is because there is a subtle little difference between each. When it defaults to 1, wsgi.multiprocess is False, where as setting ‘processes=1′ results in wsgi.multiprocess is True. This distinction exists for where one may use a means of mapping across multiple process groups in same server, or requests are handled across multiple servers in a cluster. In other words, one needs a way of saying the application is logically hosted in a multiprocess setup even though only one process in that particular process group. I know it may be a bit non obvious, but best I could could up with at the time.

Where does this matter? It matters if you want to use an in browser application debugger such as Paste EvalException or the one from Werkzeug. This will not work in a multiprocess setup as it relies on requests going back to the same process. In your setup the requests will go back to the same process, but debuggers such as EvalException think it is multiprocess setup and will not allow you to run it.

So check out the ConfigurationDirectives document on mod_wsgi wiki as well as the DebuggingTechniques document.

BTW, you might also look at the display-name option for WSGIDaemonProcess for mod_wsgi 2.0. Use that and ‘ps’ can be used to distinguish each users processes rather than them all appearing as being named ‘httpd’. Finally, you might also look at VirtualEnvironments document on wiki and setup things so that each user is working out of a Python virtual environment constructed using ‘virtualenv’. That way it is a lot easier for them to install their own Python packages.

]]> By: Deploying Django | David Cramer's Blog http://www.davidcramer.net/code/django/108/setup-mod_wsgi-for-django-and-shared-hosting.html#comment-19519 Deploying Django | David Cramer's Blog Sun, 23 Mar 2008 01:35:45 +0000 http://www.davidcramer.net/code/django/108/setup-mod_wsgi-for-django-and-shared-hosting.html#comment-19519 [...] Apache 2.x + mod_wsgiYou can see my configuration example. [...] [...] Apache 2.x + mod_wsgiYou can see my configuration example. [...]

]]>