On Mon, Jun 14, 2010 at 3:56 PM, Stuart <[email protected]> wrote:
> I have to say, figuring out this error has been the low point of my > django career thus far, and incredibly boring (my love for django is > pretty much untarnished, though). I think I need a django mentor to > teach me things like how track down what's going wrong in situations > like this. The interactions between apache, wsgi, django, psycopg2, > etc are fuzzy to me. Bruce, is this why you run lighttpd+fastcgi?? If > switching would make this problem go away, I'm game and getting gamer > all the time. ;) > This is *exactly* why I prefer lighttpd & fastcgi. That way I can run my servers in completely separate virtualenv/buildout sandboxes, and be completely certain that memory is not being shared, threads aren't getting tangled, and ... most importantly *debugging is much easier*. I happily sacrifice a tiny bit of theoretical performance from Apache in return for those benefits. Also for being able to restart stores separately from one another. -- Bruce Kroeze http://www.ecomsmith.com It's time to hammer your site into shape. -- You received this message because you are subscribed to the Google Groups "Satchmo users" 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/satchmo-users?hl=en.
