Include deployment suggestion in documentation

It would be helpful if the WhiteNoise documentation demonstrated how to actually deploy a Django application.

From reading the docs I would guess you’re suggesting to actually run python manage.py runserver directly. In other words, say with Docker, you would come up with 2 containers, one for Django and one for Postgres, in a simple case. Is that really it? 😟

If not, how would a setup look like that used uWGI or gunicorn (without Nginx or Apache, obviously)? The Django docs unfortunately talk about combining, e.g., uwsgi with Apache or Nginx just as if that were the only good solution.

[bittner]

Thanks, Dave, for the instant reply. Happy New Year, by the way! 🍾

No, really, “once you’ve got the wsgi app deployed” is a hard task for many developers. Unfortunately, it’s not done with “do a web search for ´django docker´”.

What I suggest is not doing something that is out of scope of this app and its documentation. It’s avoiding and doing away with misunderstandings, and instead pointing into the right direction. Also, because WhiteNoise changes the way we think about deployment best practices (i.e. web proxy for static files) it’s more than just “provide simple static file handing” as far as the docs are concerned.

I’ve tried to point out that the current documentation may mislead developers into thinking runserver is - finally! *sic* - a valid option for production. Actually it’s not.

Pure uWSGI, Pure Gunicorn

Can you draft your pure Gunicorn deployment in this ticket and we try to figure out how to best promote a “correct way with WhiteNoise”? In my opinion there are two options:

• Extend the Django documentation for deployment with Gunicorn and deployment with uWSGI, and point to those updated docs, or
• Add sample deployment configurations for Gunicorn and uWSGI in the WhiteNoise docs, and maybe point to those chapters from Django’s deployment documentation chapters.

Option 2 may also translate to:

• Move all common deployment information from the chapters “Using WhiteNoise with Django”, “Using WhiteNoise with Flask”, “Using WhiteNoise with any WSGI application” into a single chapter dedicated to “New-style Deployment” without web proxy.

[subodh-malgonde]

@bittner I figured it out. I have posted details here https://github.com/evansd/whitenoise/issues/219. Let me know what you think.