Serving HTML report to browsers with `--real-time-html` server

[NattyNarwhal]

One pain point we've been having with using GoAccess on remote servers is there's a few moving parts to serve the real-time HTML report. We need a web server running to serve the HTML report (sometimes you can reuse an existing one, but this might not necessarily be the case), and obviously it needs GoAccess running for the WebSocket.

For cases like this where you want to view the report from a remote system, in a browser with minimal fuss, I'm thinking it might be possible to use the existing WebSocket server for this - just serve the HTML report instead of only serving a WebSocket. This would make it easier to be able to serve it with just a single command to start GoAccess (and make it easier to manage if you want to leave it running too).

I'm currently implementing this, though it has some problems - i.e. sometimes the existing socket send for WebSockets will drop, likely because it wasn't designed for sending whole files. If this is a feature that you want upstream, let me know.

[allinurl]

That sounds like a cool idea, sending the HTML report over a WebSocket. but it seems like you'd need a client (maybe the report itself?) hosted on a web server to serve the page and open a connection to the GoAccess WebSocket server?

[NattyNarwhal]

WebSockets work over HTTP, so what could be done is instead of failing on any requests that don't upgrade to WebSockets, it could serve the HTML report back, since most of the work of the web server is there.

Since you're interested, I'll file a PR soon.