On Nov 18, 12:52 am, Graham Dumpleton <[email protected]> wrote: > In OP's setup though since they don't have control of their Apache > even less likelihood they can get a nginx front end proxy for it > going. :-) > > Graham
That could be true, although the current workload is next to nothing so the current setup will be fine. It is not so much that things aren't configurable, it's just that bothering the admins too much will cost my partner money :) Today my new mod_wsgi configuration was accepted and implemented. When things really get rough I could use memcached and I'm confident that the installation would be no issue. The current goal is to develop one CMS system - in Python of course - which basically is a frontend for every users MySQL database. The users will get a custom site also in Python. Does anybody have any tips for this type of setup? I'm not really sure what is the right way to share libraries. At the moment the communication is very simple, webservice like. A site will issue a request to the CMS system and the system will query the right database and return a nice JSON model of variables the site can use. For the easy stuff this works fine, although I'm afraid this may not be enough for more complicated situations. Daan -- You received this message because you are subscribed to the Google Groups "modwsgi" 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/modwsgi?hl=.
