Re: [Django] #27749: Documention change gunicorn deployment

[Django]

#27749: Documention change gunicorn deployment
-+-
 Reporter:  JorisBenschop|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.10
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Marten Kenbeek):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 The docs explicitly mention:

 > It requires that your project be on the Python path; the simplest way to
 ensure that is to run this command from the same directory as your
 **manage.py** file.

 If your project is on your python path, the wsgi file has a relative
 location of `myproject/wsgi.py` (at least when using the default project
 template). This translates to an import path of `myproject.wsgi`, so the
 documentation is correct.

 If `gunicorn myproject.wsgi` can't find your wsgi file, it's because your
 python path does not contain the root of your project, or your wsgi file
 has a non-standard location.

--
Ticket URL: 
Django 
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/071.006e8d90f2223885151e511b6d78d6b3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27749: Documention change gunicorn deployment

[Django]

#27749: Documention change gunicorn deployment
-+-
 Reporter:  JorisBenschop|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by JorisBenschop):

 * status:  closed => new
 * resolution:  worksforme =>


Comment:

 well the doc highlights an example usage that crashes (despite that other
 text is correct. This difference in explanation creates a discrepancy and
 thus confusion). I think this could be improved. Therefore I suggest to
 replace the
 {{{
 gunicorn myproject.wsgi
 }}}
 by
 {{{
 gunicorn wsgi
 }}}

--
Ticket URL: 
Django 
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/071.d007d7fe028a8dd993354cf3ee3b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27749: Documention change gunicorn deployment

[Django]

#27749: Documention change gunicorn deployment
-+-
 Reporter:  JorisBenschop|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.10
 Severity:  Normal   |   Resolution:
 |  worksforme
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham):

 * status:  new => closed
 * resolution:   => worksforme


Comment:

 I think "gunicorn just needs to be called with the location of a module
 containing a WSGI application object named application" explains the usage
 well enough If that is unclear and you want to propose some clarification,
 please do.

--
Ticket URL: 
Django 
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/071.b3298604878102f4b76c14e5693b8347%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.