Open fishman opened 5 years ago
Hi, make sure the client connects to Pushpin. :)
Hey there,
I'm hitting the same issue and I think I am missing something very obvious here.
My setup is as follows:
pushpin container
<- django container with supervisord/gunicorn and 3 workers
-> nginx -> frontend
The nginx
container proxies all requests that come in the /api/
url to the django container. I can ping the pushpin
container from the backend
container.
Am I correct in saying that I need to make the nginx
server forward the URLs defined in the asgi.py
file to the pushpin
container ?
I never worked with pushpin before, but reading their documentation it seems that it should just plug in and work without too much configuration, so clearly I'm missing something obvious.
I'd gladly make a PR with more detailed steps for pushpin
setup if I get it to work :D
Hi @bogdan-calapod, Pushpin goes in front of the Django app, not behind it. Nginx should forward requests to Pushpin, and Pushpin should forward requests to the app.
Oooh, that makes sense - from what I can see, pushpin forwards everything to the backend specified in the routes/
file, and only does streams or anything else if the backend server instructs it to. I'll tinker with it a bit and see if I make it work. Thanks!
Managed to get it working - opened #113 with what I felt was missing in order to get PushPin working :D
I see the events being created in the
django_eventstream_event
table. I setup a grip_url to be my ip on the backend ofhttp://pushpin:5561
and I have a daphne running.However looking at the access log of my pushpin server there is absolutely nothing happening on there. And the client that is connected to daphne does not receive any messages.
Is there any way I can debug this? The setup works fine if I just use
runserver
but that obviously doesn't work in production.