Allow proxy through master

[rrusso1982]

Being able to connect directly from your browser to the worker nodes in a multi server setup can be complex in many environments where corporate security is high or network flows are complex. Instead it can be beneficial to be able to retrieve live logs by proxying the requests through the master.

This PR implements a pull through mechanism that allows the browser to request a live log from the master. The master will then make another request to the worker node to get the last X lines from the workers log file. Those lines are then sent back to the users browser.

A de-dupping of the log lines is also applied at the browser since slow scripts or short logs in general can cause duplication in the log lines being returned when requesting the last X lines from a log file.

Also a big thanks to @mikeTWC1984 for pointing me at his previous effort put in to make this work as it was the basis for this updated version.

[justinmdudley]

Looking forward to this being available!

[rrusso1982]

@jhuckaby Any chance of getting a review on this please?

[jhuckaby]

Hey there!

I'm so sorry, but I cannot merge this PR into Cronicle. It is just way too many changes. I haven't the brain capacity to maintain this code, when future issues come in.

Please understand, I greatly appreciate your work. Open source software is amazing, because anyone can fork it and build in their own enhancements, and the fact that you chose my little project to work on is awesome! But Cronicle v0.x is in maintenance-only mode. I am no longer adding any new features, because I am hard at work on the next major version of Cronicle. It is a complete ground-up rewrite from scratch, and will have MANY of the requested features people have been asking for (including this one).

I feel terrible, because you've obviously spent a large amount of time working on this PR. I am going to add a special pull request template into Cronicle's GitHub repo TODAY, which explains my policy on merging PRs, and I'll also add in a message into the main README as well. I'm so sorry I didn't do this before now.

Thank you, and again, deepest apologies.

-- Joe

[mikeTWC1984]

@rrusso1982 just modify installation script below to use your fork and leave it under the issue you opened, so whoever needs this capability will be able to use it.

mkdir -p /opt/cronicle
cd /opt/cronicle
curl -L https://github.com/jhuckaby/Cronicle/archive/v1.0.0.tar.gz | tar zxvf - --strip-components 1
npm install
node bin/build.js dist

[soraxas]

Thanks for implementing this, really appreciate it! But just as a question is this extra line a typo?

[ericma15]

@rrusso1982 hey i use your fork. But it seems not take effect.
Still say,connect https://xxxx:3012.
BTW,i use benhind a reverse proxy.

I did it.
But some thing strange happended. The CPU chart not update at all. But I can see websocket transfer data.