Talin wrote: > Just a comment on this whole bluehost issue. > > I too was misled by the TurboGears documentation, and chose bluehost as > my hosting provider. What I have discovered is the following: > > 1) Bluehost does not have mod_proxy installed > 2) Bluehost does not have mod_python installed > Odd, I remember talking with a tech and he assured me that Bluehost had mod_python installed. I haven't tested. (just thought I would use it latter on. I don't run turbogears projects on there yet).
I would suggest talking to there tech support. They usually are open to stuff like this. At least in my dealings with them. > 3) There is something about the bluehost configuration that is actively > hostile to servers running alongside Apache. If I start CherryPy > listening on port 8070 (or any other high port), not only can my > connections *not* get through, but my primary web site is *disabled* > (all requests simply return "<!-- SHTML Wrapper - 500 Server Error > -->"). If I kill the CherryPy process, everything returns to normal. > 4) The version of python on Bluehost is 2.3 (admittedly not a huge > problem to overcome) > > Bluehost does have mod_rewrite and mod_fastcgi, but I have discovered > that the FastCGI solution is complex, difficult to debug, and has > unacceptably slow performance. > > I would strongly recommend removing bluehost from the list until such > time as they improve the situation. > > -- Talin > > > > > > -- Nicolas Kassis -------------- www.nickassis.net www.nickassis.net/blog --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
