#23350: mod_wsgi authentication/authorization docs result in extra memory usage
--------------------------------------+------------------------------------
     Reporter:  GrahamDumpleton       |                    Owner:  nobody
         Type:  Cleanup/optimization  |                   Status:  new
    Component:  Documentation         |                  Version:  1.6
     Severity:  Normal                |               Resolution:
     Keywords:                        |             Triage Stage:  Accepted
    Has patch:  0                     |      Needs documentation:  0
  Needs tests:  0                     |  Patch needs improvement:  0
Easy pickings:  0                     |                    UI/UX:  0
--------------------------------------+------------------------------------
Changes (by aaugustin):

 * needs_better_patch:   => 0
 * component:  Uncategorized => Documentation
 * needs_tests:   => 0
 * needs_docs:   => 0
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 I believe we should provide a copy-paste-proof example for the simple case
 of "first time I'm touching Django and Apache, how do I run my test
 project?" and shell out to mod_wsgi's own docs for anything more
 complicated.

 For that use case, we can assume that there's only one Django application.

 We just need:

 - to make sure our documentation stays internally consistent — we don't
 want the mod_wsgi auth docs to have subtle differences with the mod_wsgi
 main docs.
 - to add a warning about running multiple Django projets in the same
 server — which Apache's lovely handling of env variables makes hard anyway
 — and leave that part of the explaination up to mod_wsgi :)

-- 
Ticket URL: <https://code.djangoproject.com/ticket/23350#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.dd9e32ae437c1b6d7742a3ca40dbf8af%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to