On Sat, 2009-01-10 at 10:37 +0000, Alan wrote: > Thanks Graham, indeed I was being stupid, I didn't realise that mac > leopard holds apache 2.2 now... > > > About docs, where can I find something about apache2 + mac osx + > mod_wsgi in http://docs.djangoproject.com or google? All I get is > puzzles with missing pieces...
So, here's the thing: one day we'll include a short piece on the really basic setups for mod_wsgi in the Django docs, similar to what we do for mod_python. We'll do that because somebody will write it (or one of the rest of use will eventually find the time). However, it will never replace the mod_wsgi documentation. Deliberately. The Django project shouldn't have to provide that kind of one-stop replacement. The Django documentation is about using Django. For documentaiton on using Apache, there is wonderful documentation provided by the Apache project. For documentation on using Python, python.org is the source. For documentation on using mod_wsgi, there is the mod_wsgi project at Google. You can see the pattern here. Particularly when external resources provide good documentation (python, Apache, mod_wsgi, mod_python, etc, etc), we absolutely should dispatch to them (and Google and Yahoo are our friends in this respect). I think it's absolutely fantastic that somebody like Graham Dumpleton spends so much time on a list like django-users when he doesn't have to. It provides a lot of people with a lot of help. I also find it to be a form of highly wasteful time usage, since most of the questions have more appropriate forums and there's not always the "teach a man to fish" result falling out at the end. Glad Graham does not, not about to pick up the slack if he ever decides to ask people to come to the appropriate lists to ask questions. We document how to use Django. We also go the extra mile and include a bunch of other documentation to help out people just starting out (for example, a lot of examples and explanations are somewhat verbose because we're helping out Python beginners, which aren't our primary audience), but it always has the slight side-effect of actually making the Django documentation harder to use. The extra explanations of stuff that isn't Django related often tends to obscure the actual useful Django documentation. I'm not intending to be harsh here, but that is the reality. If somebody is going to develop using Apache, then the same as if they're going to use HTML or Javascript or Python or CSS or Eclipse or vim or whataver, they have to be spend some time reading and learning about that tool. Yes, it's a huge learning curve to develop web applications. It's actually hard stuff. This isn't targeted (only) at you. It's a general complaint against people hoping Django will provide recipes for doing stuff that is out of scope and should remain so. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
