On Fri, 2007-16-02 at 15:08 +0100, Diez B. Roggisch wrote: > On Thursday 15 February 2007 23:36, iain duncan wrote: > > > 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. > > > > Now that said, you could do as I am planning for some clienst and write > > a turbogears app that provides an admin interface on one machine ( my > > rented server ) and then provide an additional app in python that > > generates a whole wack of static html files and or php+static files and > > installs said files on cheapo hosting. I'm exploring this avenue right > > now for a number of reasons: > > So basically you're wget'ting all your content? Because I fail to see where > any dynamicity (unless explicitely written for e.g. mod_python and > pre-deployed) is supposed to come from with this.
That's the idea. They get two sites. One is a TG app that is dynamic, and runs on my server. The other is a rendered static or minimal dynamic site that the TG app and the helper app put on their server. The minimal dynamic content is not done through TG. This only is useful if you have a case where the dynamic aspect is used vastly less than static viewing of the page. But take a simple CMS where the only real dynamic aspect of the public site is say a comment box and contact form. Those can be relayed to my server once a day through some trivial php code, while my client probably only updates their site say once a day to once a week. The time they spend doing this is a non-issue to my server load and the TG app can be turned off when they are done. Like I said, it's only practical for a certain kind of job, but I happen to get that kind of job more often than not. What I'm selling is a heavily customized *admin* interface to a cms. What the CMS makes just doesn't need TG running it for every client view. If there is a mixture, it's easy enough to still distribute load by putting only the db hits on my server and pulling in content with server side includes and such like. Iain --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
