I was configuring it before without using WSGIApplicationGroup but I was getting:
RuntimeError: class.__dict__ not accessible in restricted mode Do you have any example for setting up multiple aliases for a single app and how to setting up multiple apps behind same server? Regards On 9 jul, 10:48, Alessandro Molina <[email protected]> wrote: > Using the WSGIApplicationGroup %{GLOBAL} has some side effects due to > importing modules globally instead of for each application. This > causes some problems with modules that use global variables or > monkeypatching. > > I would suggest you to set up multiple Directory directives, one for > each .wsgi each with its own DaemonProcess to avoid having issues > related to the global python interpreter. > > 2011/7/9 Juan Antonio Ibáñez <[email protected]>: > > > > > > > > > Hello! > > > I'am trying to set up a second release of my app behind my prod > > server using Apache+mod_wsgi. I am always getting 404 error from > > Apache and I cannot find any error on Apache logs. The same app runned > > with 'paster serve' works without problems on the same server. I also > > tried to setup a new alias for old release instead for new one, > > getting 404 error too. My apache conf seems: > > > ... > > WSGIApplicationGroup %{GLOBAL} > > WSGIDaemonProcess ceaf threads=10 processes=3 > > WSGIProcessGroup ceaf > > WSGIScriptAlias /ceaf /usr/src/tg2env/ceaf/apache/ceaf.wsgi > > WSGIScriptAlias / /usr/src/tg2env/ceaf/apache/ceaf.wsgi > > WSGIScriptAlias /ceafv2 /usr/src/tg2env/ceaf/apache/ceaf.wsgi > > WSGIScriptAlias /ceafv3 /usr/src/tg2env/ceaf/apache/ceaf.wsgi > > WSGISocketPrefix /var/run/wsgi > > ... > > > '/ceaf' works, '/' works but '/ceafv2' and '/ceafv3' return 404... > > Any idea? -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
