#795: Comment on docs/deployment/mod_python.html
--------------------+-------------------------------------------------------
Reporter: maram | Owner: anonymous
Type: defect | Status: new
Priority: lowest | Milestone:
Component: Docs | Version: 0.9a4
Severity: normal | Resolution:
Keywords: |
--------------------+-------------------------------------------------------
Comment (by [EMAIL PROTECTED]):
How do the comments found at:
http://phirate.exorsus.net/wiki/doku.php?id=101_practical_turbogears_tips
effect this guide?
For those that would rather not click:
'''I'm going to go production using apache and mod_python!'''
Oooohhh no you’re not. You think you are, you might even get it
working according to the instructions on the website. But you are doomed.
The reason you are doomed, is because SQLObject caches values, and if
you turn off caching, your database will die a horrible query-intensive
death.
And since SQLObject caches values, and you’re almost certainly running
apache2 in some form of multi-process setup, each process loads the
turbogears instance, and each changes the database independently, and the
caches of the other ones don’t get updated, and it all turns into a
steaming pile of confusion. Usually, slowly and subtley with od bugs like
things not updating properly if you use a redirect and that kind of thing.
The answers to this problem are hard to locate. Everyone is raving about
turbogears but I have yet to locate information on a good, solid, reliable
production setup. Until then, I’m using apache2 with mod_proxy to the
cherrypy instance. You can improve on this by mapping the static/ subtree
directly in apache. I’ll update this when I figure things out. It’s
*possible* that a multi-threaded server may keep things in sync properly,
it is almost certain that a later version of SQLObject will resolve the
issue in a better way (or at least fail obviously so you know it’s not
gonna work).
I'm figuring if SQLObject can't really handle it, then this setup is
somewhat doomed.
--
Ticket URL: <http://trac.turbogears.org/turbogears/ticket/795>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears Tickets" 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-tickets
-~----------~----~----~----~------~----~------~--~---
