News for hackers. Stuff that matters.
Re:Deploying Django on Heroku by maaku on Saturday September 17, 2011 @01:18PM (#3008506)
This is running via runserver, right? Don't use this for production.

There are some nice pure-Python web servers though. To someone who knows more about Heroku's stack, if I replace “manage.py runserver” with, say, CherryPy, would there be any Heroku-specific performance issues to consider?

Re:Deploying Django on Heroku by lamby on Saturday September 17, 2011 @01:47PM (#3008563)
(I would use gunicorn)
Re:Deploying Django on Heroku by kylefox on Saturday September 17, 2011 @03:01PM (#3008688)
Good plan. From the Django documentation:

"DO NOT USE THIS SERVER IN A PRODUCTION SETTING."

(https://docs.djangoproject.com/en/1.3/ref/django-admin/#runs... )

Re:Deploying Django on Heroku by ymir on Saturday September 17, 2011 @03:26PM (#3008735)
We made a nice recipe for production-ready Djanogo setup on Heroku http://www.askthepony.com/blog/2011/07/getting-django-on-her...
Re:Deploying Django on Heroku by abhiomkar on Sunday September 18, 2011 @12:52AM (#3009523)
gunicorn server will work, this makes it production ready.

Please replace runserver line with the below line in your Procfile

    web: bin/gunicorn_django --workers=4 --bind=0.0.0.0:$PORT django_project/settings.py
Re:Deploying Django on Heroku by MostAwesomeDude on Saturday September 17, 2011 @06:29PM (#3009006)
I have done this with Twisted and have yet to see any problems.

In your requirements.txt, add "Twisted". In your procfile, try something like:

    web: bin/python ./twistd -n web --port=$PORT --wsgi fully.qualified.app.name