Thanks so much Wyatt - it seems it was permissions related. What I had not realised was that even though I had the user set as my own, Apache still needed permissions to access some of the files to run and I had to make sure the wsgi file was marked as executable correctly. That done, it seems fine now (well, at least it runs, I'm dealing with other problems at the moment).
Thanks again for pointing me in the right direction on this, Ben On 6 October 2011 19:48, Wyatt Baldwin <wyatt.lee.bald...@gmail.com> wrote: > This is what my typical mod_wsgi config looks like: > > WSGIDaemonProcess myapp user=wyatt home=/home/wyatt/envs/mayapp > display-name=myapp > WSGIScriptAlias /myapp /home/wyatt/envs/myapp/bin/app.wsgi > <Location /myapp> > WSGIProcessGroup myapp > </Location> > > Maybe you need to add a Location section? > > Also, I'd double check the permissions on /home/benjamin (should be > something like 701). > > -- > You received this message because you are subscribed to the Google Groups > "pylons-discuss" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/pylons-discuss/-/Vi2OHd403dkJ. > > To post to this group, send email to pylons-discuss@googlegroups.com. > To unsubscribe from this group, send email to > pylons-discuss+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/pylons-discuss?hl=en. > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
