gunicorn in docs
Wim Feijen
After watching glyphs talk [1], do we want to add a gunicorn
installation instruction to the installation docs? What is your
opinion?
Wim
[1]: http://blip.tv/djangocon/keynote-glyph-lefkowitz-5573264
Paul McMillan
django work with gunicorn, and are willing to keep them up to date, I
see no reason we shouldn't include them. It's what I use, and has the
advantage of being very, very easy to get working.
-Paul
Russell Keith-Magee
I agree with Paul that this would be a good contribution -- however, I
would provide one piece of guidance.
There's a fine line between documentation for how to get Django to
work with Gunicorn (or any other web server for that matter), and
providing documentation for Gunicorn itself. The right place for
canonical Gunicorn documentation is the Gunicorn project, not Django.
There is certainly room for documentation on how to get Django running
under Gunicorn. However the bits in Django's documentation should be
restricted to the Django-specific parts -- Django-specific settings,
configuration requirements, and maybe some guidance on how Django
interacts with any tuning parameters (e.g., Django uses a lot of X,
but not much Y, so you'll get better performance if you configure the
web server to allocate extra X at the expense of Y).
If you find yourself writing explanations for every setting in
Gunicorn, then you should be directing the reader to Gunicorn's
documentation on those settings; and if Gunicorn doesn't have adequate
documentation on those settings, then that's a contribution you should
be making to Gunicorn.
Yours,
Russ Magee %-)