Justin Karneges

Also, `publish_http_stream` publishes data only to clients that are using the HTTP streaming transport. To publish to clients that are connected with the WebSocket transport, you need to publish a...

See https://pushpin.org/docs/usage/#websockets . There's a PHP example.

I'm guessing that error is coming from `$in_events[0]` ? This script is meant to be invoked by Pushpin, in which case events will be provided and the code should be...

`logrotate` should work. Send `SIGHUP` to rotate. Alternatively you can use the `-m` command line argument to pushpin to cause almost everything to output to stdout, which you could then...

I suppose this ought to be made configurable, and the size limits between HTTP and ZeroMQ inputs should be more consistent. However, large messages are not recommended as they can...

With the HTTP streaming transport (which you are using if you're doing SSE), it is possible to use [reliable streaming](https://pushpin.org/docs/advanced/#reliability) to set a URL to fetch data from and then...

Hi, It's best to run separate containers if you can. This is typically how containerized deployments are done. It's also a good way to deploy Pushpin, because multiple backend instances...

Pushpin uses DNS lookups to resolve targets, so service URLs should work.

Proposal: a `set-header` param on `Grip-Link` specifying a request header using the form `name:value`. For example: ```http HTTP/1.1 200 OK Grip-Hold: stream Grip-Channel: foo; prev-id=1 Grip-Link: ; rel=next; set-header="Authorization:Bearer {token}"...

While we're at it, consider adding a generic header to indicate whenever a request originated from the proxy. This could be useful for trusting the request URI, as well as...