Re: Wsgi path problem: deploying on a production server

Thanks for your help; it's good to see how others configure Apache. I'll give the Location block a try. I'm not sure that will solve my problem, because you still have the WSGIScriptAlias with root . That means all traffic to your site should go through python and wsgi. My app works fine that w

Re: Wsgi path problem: deploying on a production server

I believe you can accomplish handling specific locations with different modules by using the Location and SetHandler directives and using Alias for static content. Notice how I activate the "server-status" module on a sub directory of a site, and how I handle static content all from one Apache

Wsgi path problem: deploying on a production server

I was able to deploy my django app on a new server with this configuration option: WSGIScriptAlias / app1.wsgi Everything works beautifully (so I have wsgi configured properly), but the wsgi script captures all traffic to my server, which I don't want. So I tried this: WSGIScriptAlias