#27749: Documention change gunicorn deployment
------------------------------------------------+------------------------
               Reporter:  JorisBenschop         |          Owner:  nobody
                   Type:  Cleanup/optimization  |         Status:  new
              Component:  Documentation         |        Version:  1.10
               Severity:  Normal                |       Keywords:
           Triage Stage:  Unreviewed            |      Has patch:  0
    Needs documentation:  0                     |    Needs tests:  0
Patch needs improvement:  0                     |  Easy pickings:  1
                  UI/UX:  0                     |
------------------------------------------------+------------------------
 from
 [https://docs.djangoproject.com/en/1.10/howto/deployment/wsgi/gunicorn/]
 In section "Running Django in Gunicorn as a generic WSGI application"
 there is the suggestion to run
 {{{
 gunicorn myproject.wsgi
 }}}
 However, on my server (CentOS7) at least, django-admin does not create a
 myproject.wsgi, but a wsgi.py. Problem is that you cannot run
 {{{
 gunicorn wsgi.py
 }}}
 It will fail with the cryptic "Reason: Worker failed to boot.". Instead,
 one must run
 {{{
 gunicorn wsgi
 }}}
 (so without the .py extension)

 I have not tested this on other setups, so it could be very specific.
 Still, would it be possible to make a mention of this behaviour in the
 django documentation?

 Thanks
 Joris

--
Ticket URL: <https://code.djangoproject.com/ticket/27749>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/056.dd9a64b1b2909ce7f0cb0d3b392f41a7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to