Re: Is there a better way to do Django+WSGI+Apache when using multiple virtual hosts that point to the same Django installation than what I'm currently doing?

One of my problems, as Steven mentioned in the thread above this post, is that I have to be very specific with URLs in my current setup. For example, site2.domain.com uses the same Django install as site1.domain.com, but a different application. As a result, in the urlconf I have to have something

Re: Is there a better way to do Django+WSGI+Apache when using multiple virtual hosts that point to the same Django installation than what I'm currently doing?

Your probably better off with three separate VirtualHosts in your case. They can point to the same django project but use different settings files with a different SITE_ID for each one. This would allow you to utilize the built in Sites framework. On Wed, Apr 14, 2010 at 7:08 PM, Steven Degutis

Re: Is there a better way to do Django+WSGI+Apache when using multiple virtual hosts that point to the same Django installation than what I'm currently doing?

If you don't mind me jumping in here, I have a followup question (related context: I'm a django newb, this is day 3 for me) -- if you use ServerAlias, how do you specifically set django to recognize the different subdomains when a website is accessed? The urlpatterns seem to only match everything a

Re: Is there a better way to do Django+WSGI+Apache when using multiple virtual hosts that point to the same Django installation than what I'm currently doing?

I'm assuming you are running all three of these projects on the same machine. You can use the ServerAlias directive in your config. It would look something like this ServerName host1.domain.com ServerAlias host2.domain.com host3.domain.com DocumentRoot /var/www/whatever/ WSGIScriptAlias /host1s

Is there a better way to do Django+WSGI+Apache when using multiple virtual hosts that point to the same Django installation than what I'm currently doing?

Hello, I have multiple virtual hosts pointing to the same Django project. So something like: host1.domain.com host2.domain.com host3.domain.com each point to the same Django project because although it was required that host1 host2 and host3 should get their own hostnames, none of web apps the