On Feb 20, 2006, at 3:28 PM, gabor wrote: > 1. except that it was not meant for that, are there any fundamental > problems with the "runserver"-webserver?
Using runserver in production is like driving your car on a spare tire. It'll work, but when it blows up in your face someone's going to get hurt. Seriously, here's just a few reasons you shouldn't use it in production: * the dev server can only handle one request at a time (no concurrency) * since it handles everything in Python including the low-level transport, it'll be very slow compared to a real server * it's likely got all sorts of security holes since NOBODY uses it for public sites * all the cool kids will laugh at you. There's no reason you can't use Apache2 on RedHat8; just built it yourself (which is not nearly as hard as it sounds; a standard configure/make/make install dance does it fine). Or take a look at lighttpd+fcgi. Trust me -- you think you'll be happy using the dev server now, but something serious will go wrong and you'll end up installing a real production environment anyway. Do it now and save yourself the heartache. Jacob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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/django-users -~----------~----~----~----~------~----~------~--~---
