On Jan 14, 4:28 pm, "Diez B. Roggisch" <[email protected]> wrote: > To summarize: you are frustrated because you chose > a deployment strategy at a time where no such thing was needed.
"Deployment strategy", wow, so that's what the marketing guys call it nowadays. Sounds a bit like an argument for a bloated system, just right if you happen to drive a "grown" (bloated) IT department: There are a couple of guys doing the hard everyday deployment work, and there is a small group of clear minded responsible people figuring out the strategy for them ... My situation is a bit different: It must run with apache. Call it "deployment strategy", I'd rather call it common sense, and maybe I'm not alone with this demand. > And because that failed, you condemn the whole project > as being essentially worthless as a base-technology to write webapps. Yes, because the failure demonstrates that the makers of the project either a) never tested their product (which naturally comprises the docs) or b) just don't care. And if it starts like this it's probable that the same attitude will appear at other places as well when one really starts to use TG. > Yes, mod_wsgideploy is crap. ... Ok, let's forget the config file generator. This page looks good to me: http://code.google.com/p/modwsgi/wiki/QuickConfigurationGuide WSGIScriptAlias and DocumentRoot settings - makes perfect sense, but there's more to do: > Me personally worked with > http://code.google.com/p/modwsgi/wiki/IntegrationWithPylons Now the story gets a bit complicated, we have to "construct .. a WSGI application stack based on a specific configuration file", which introduces a new /usr/local/pylons/ directory. So after python, mod_wsgi, apache there is another player involved in order to produce a 'hello world'. At this point a diagram would make enormous sense .. not only for beginners like me but maybe also for the designers of a web framework. Anyhow, as an application developer I call this "internal technical details" and I'd expect a framework to _hide_ it from me; i.e. make a sensible decision that's set up as a default and works for most installations. > .. your conclusions are over-reaching and offending. Well, I met several people praising python and django, and when being asked about TG mumbling something about "installation problems". So consider what I'm doing here as a translation of that mumbling ... -- 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.
