I fail to see what's so complex of uwsgi for a simple deploy, my typical configuration file has 8 lines
On 3/17/17, Antonis Christofides <[email protected]> wrote: >> Thanx you very much, i've spent days on this issue > I'm sorry to hear that, especially because when I was using uwsgi I was > also > spending days for various issues. All this pain went away when I started to > use > Gunicorn. You can read more about that in > https://djangodeployment.com/2017/01/02/which-wsgi-server-should-i-use/. > > Regards, > > A. > > Antonis Christofides > http://djangodeployment.com > > On 03/17/2017 09:19 AM, valerio orfano wrote: >> I want to thank Melvyn publicly, without his support i wouldn't succed! >> >> unix:/// in the uwsgi.ini file DOES NOT work (at least in Centos) >> >> insted unix:/ WORKS OUT >> >> Thanx you very much, i've spent days on this issue >> >> >> On Thursday, March 16, 2017 at 8:58:52 PM UTC+1, Melvyn Sopacua wrote: >> >> On Thursday 16 March 2017 11:04:53 valerio orfano wrote: >> >> > http://uwsgi-docs.readthedocs.io/en/latest/Nginx.htm >> <http://uwsgi-docs.readthedocs.io/en/latest/Nginx.htm> >> >> *sigh* >> >> >> >> http://nginx.org/en/docs/http/ngx_http_uwsgi_module.html#uwsgi_pass >> <http://nginx.org/en/docs/http/ngx_http_uwsgi_module.html#uwsgi_pass> >> >> >> >> unix:/path/to >> >> >> >> Maybe unix:/// works, maybe it doesn't. But file:/// is supposed to be >> the >> exception to the URI rules, not the rule itself. >> >> >> >> Also, just providing a plain path (socket = /var/run/uwsgi/myapp.sock) >> in >> uwsgi.ini works. >> >> >> >> Of course, it will try to create the socket under the user uwsgi runs >> as, >> so permissions for the directory need to allow that. >> >> -- >> >> Melvyn Sopacua >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] >> <mailto:[email protected]>. >> To post to this group, send email to [email protected] >> <mailto:[email protected]>. >> Visit this group at https://groups.google.com/group/django-users. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-users/b6cfe3f2-ca74-44b3-830a-25c5f3c8afc3%40googlegroups.com >> <https://groups.google.com/d/msgid/django-users/b6cfe3f2-ca74-44b3-830a-25c5f3c8afc3%40googlegroups.com?utm_medium=email&utm_source=footer>. >> For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "Django users" 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]. > Visit this group at https://groups.google.com/group/django-users. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/be7e5d19-40b4-4d8a-c4e3-1812c634b090%40djangodeployment.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django users" 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]. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CALn3ei04gX2%2BVWkYfTiykX4ONAQVrzswJG8HWyrt%3DtYemvwZPw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
