Home » Odeon Blogs » Stefan Talpalaru, CTO »

introducing django-cherrypy-odeon

introducing django-cherrypy-odeon

Our favorite Django deployment strategy is to run the WSGI server from cherrypy behind cherokee. Here's the result of this experience - django-cherrypy-odeon. You can now enjoy the stability and low resource consumption of cherrypy as a production server along with a very fast, threaded, development server replacement. No more AJAX problems with concurrent requests while keeping the familiar devserver output. Enjoy the multitude of options and have fun benchmarking processes against threads (spoiler: the GIL sucks).

We stand, of course, on the shoulders of giant snippets. Besides exposing more cherrypy options, we added the 'runserver_cp' command and a patched version of wsgiserver that outputs the requested paths when tickled in a certain way.

The sysadmins among you might want to check out the init scripts provided for the dreaded Debian and the wonderful Gentoo. Pardon the common shell script doing the heavy lifting, but we think that code duplication is a sin.


Category: django-cherrypy-odeon



Leave a Comment :

(required)


(required)




(required)




(required)






Leave a Comment


Page generated in: 0.14s