Joshua J. Kugler schrieb: >> On Feb 15, 2:49 pm, "Diez B. Roggisch" <[EMAIL PROTECTED]> >>> No, it won't work that way. You have to code in the environment you want >>> to deploy in. > Umm...please correct me if I'm wrong, but aren't there facilities in > TurboGears for making eggs out of your TG project precisely so you can put it > on another server once you're done developing?
Yes, but the server needs to provide the facilities to install & run TurboGears. Most cheap shared web hosting environments don't support this, because they don't meet one of these requirements: 1) Python >= 2.3 must be installed (and working!). 2) The user must be allowed to install additional modules. 3) The platform must be supported by the available binary eggs for TurboGears components (i.e. cElementTree, RuleDispatch etc.) or you must be able to compile them yourself for the target platform. 4) It must be possible for the user to have long-running processes (i.e. the CherryPy server). 5) It must be possible to run a process that listens on a INET port (normally 8080). 6) The user must be able to configure the webserver to connect to the CherryPy server (via mod_proxy, mod_python, or fcgi/scgi). This is all no problem if you have full controll over the server, like you have, e.g., with virtual private hosts, but generally in shared environments at least one of these requirements isn't met. > You need to code in a similar environment, yes, because you need python > installed, etc. Unless Diez meant you need TG installed where you deploy. I think that's what he meant. Chris --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
