On Fri, Jan 14, 2011 at 8:29 AM, bvdb <[email protected]> wrote: > Now, before the first 'hello world' from the apache webserver there > was some configuration to do for the wsgi interface. PHP works easily > in this aspect, but one can accept a bit more effort for a less > popular but superior platform.
I think the docs were rough around the edges, but 2.1 looks a lot better. On the specifics of deploying to Apache / mod_wsgi... It can be a bit hairy, but its something you only have to figure out once. I've read lots of reviews of different software packages where the reviewer spends half the article talking about the setup process. To me, the setup is a detail. The only important thing about setup is "Can it be done reliably?" Because you only do the setup once. I've developed a couple of TurboGears based sites and I can basically use the same template and pattern for deploying to mod_wsgi. It did take me a solid 8 hours to get that sussed out, but its largely behind me. So I'm not saying its not important to have good setup docs... but I guess that is what I'm saying. I've spent a lot more time (and will spend way more time in the future) looking at API's and writing code than I will worrying about getting mod_wsgi to work correctly. I'm very happy with TurboGears on mod_wsgi. There was a learning curve, but now that I'm starting to get over the learning curve, its very nice. -- 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.
