Re: Deploying django, channels and websockets with nginx and daphne

2020-02-26 Thread Daniel Wilcox
At a quick glance -- your proxy_pass statement is pointed at the nginx listener instead of at the upstream. Change this: proxy_pass http://0.0.0.0:8090; To this: proxy_pass django; Hope that helps, =D On 2/26/20, Larry Martell wrote: > I've posted this to the django mailing list and to stack

Re: Deploying django, channels and websockets with nginx and daphne

2020-02-26 Thread Francis Daly
On Wed, Feb 26, 2020 at 05:55:02PM -0500, Larry Martell wrote: Hi there, > upstream django { > server unix:/run/daphne/devAppReporting.sock; > } > > server { > listen 8090; > location / { > proxy_pass http://0.0.0.0:8090; Changing that to "proxy_pass http://

Deploying django, channels and websockets with nginx and daphne

2020-02-26 Thread Larry Martell
I've posted this to the django mailing list and to stack overflow, with no replies so trying here. I am trying to deploy a django app that uses channels and websockets, with nginx and daphne. When I was using uwsgi, here was my nginx file: upstream django { server unix:/run/uwsgi/devAppR

Re: Nginx location - Distinguish requests by arguments or queries

2020-02-26 Thread Francis Daly
On Tue, Feb 25, 2020 at 05:06:15PM +, Francis Daly wrote: > On Tue, Feb 25, 2020 at 07:05:05AM -0500, stmx38 wrote: Hi there, two corrections to my suggestion... > > For location /test we should permit only POST, for /test?doc we should > > permit only GET methods. > Something like: > > ==