Python Projects in Users’ Home Directories with wsgi | Code Spatter…

Before arriving at the solution in my post I tried using an .htaccess file and the directives I tried weren't supported in .htaccess. I didn't read the part about AddHandler so I missed that.

Something with either WSGIDaemonProcess or WSGIProcessGroup from the code in the blog post is making those applications work in daemon mode. It seems like any wsgi file that is touched will result in the code being reloaded for that project.

http://code.google.com/p/modwsgi/wiki/Configura...

The approach here, using AddHandler and multiviews matching, is to overlay, or insert, the WSGI application into the directories containing the static files. It results in a slighter cleaner configuration that using WSGIScriptAlias and then trying to overlay static resources on top of the WSGI application. Using AddHandler means you can add both WSGI applications and static files without needing to change Apache configuration and restart Apache.

I have ignored daemon process groups for the moment, but can still be used in conjunction with this approach.

I didn't expect that WSGIDaemonProcess wouldn't expand the python_project_name. I was doing that so that each project would have a different process so touching one wsgi file wouldn't effect another project. It seemed like it was working like that.

If you can figure out a better way of doing this that would be awesome.

BTW, am still looking and will post better configuration, but to start with, using:

wsgi_processes.%{ENV:python_project_name}

for argument to WSGIDaemonProcess is wrong, as that will not be expanded. Not even sure how it is working for you, as WSGIProcessGroup would be expanded and so wouldn't match the WSGIDaemonProcess and so it should give an error that you are delegating a non existent daemon process group, when request comes in and is evaluated.