Web-server – Risks of using django manage.py runserver for production in a small scale server, for internal use

deploymentdjangoweb-server

I am writing a small web-app with django. It will have no more than 200 users, all internal to my company. I want to set it up as quickly as possible. I am new to django and web-apps.

As I read django's tutorial, they don't recommend using python manage.py runserver to deploy the production server, but they don't give any reasons.

I suspect that for my very modest purposes, django's runserver will do fine. Am I correct? What risks am I running?

Best Answer

From the manage.py documentation:

DO NOT USE THIS SERVER IN A PRODUCTION SETTING. It has not gone through security audits or performance tests. (And that’s how it’s gonna stay.

That's all you need to know to make a decision on this.

If you're deploying a python web app, even for a low-load, internal-use only project, it is still very much worth the extra work to learn a proper way to host the application, as it's quite likely that you'll need to use those skills at some point in the future.

Related Solutions

HTTP 500 error from POST reuqest to django vai WSGI and apache

Ok, so once again we come down to user error. At some point the problem changed because I changed some of the code above, so that

def post_authentication_api(request):

became

def post_authentication_api(self, request):

this doesnt work because as Graham said at the django mailing list

"If you ... have a 'self' first argument for a function which isn't a method of a class, it is obvious you are going to get:"

Exception Type: TypeError at /auth/post_authentication_api 
  Exception Value: post_authentication_api() takes exactly 2 arguments 
(1 given)

So after I fixed that up I came to the root of the problem (as far as I can tell) which was that wsgi was blocking sys.stdout. which I think seems fair to me, and I had some print statements in my code and this is why it wasnt running. A very simple problem that for some reason became very complicated.

Anyway, Great thanks to Graham who has helped me out for the last week on this. He has been tireless and very accommodating to someone who is quite embarrassed about the final outcome. Some votes will be coming his way for the comments and my many thanks as well.

Thanks again

Mark

Python – Django Apache WSGI – very slow production server

You could use WSGI level request/response logging as described in:

http://code.google.com/p/modwsgi/wiki/DebuggingTechniques#Tracking_Request_and_Response

to see when WSGI is entered and exited to try and validate whether issue is before WSGI application even gets invoked.

Best Answer

Related Solutions

HTTP 500 error from POST reuqest to django vai WSGI and apache

Python – Django Apache WSGI – very slow production server

Related Topic