Re:Rtail – Terminal output to the browser using Unix pipes
by spinlock on Wednesday July 08, 2015 @01:12AM
(#9849928)
It doesn't go to a browser (unless you use something like https://keymetrics.io/2015/06/10/pm2-ssh-expose-a-fully-capa...) but `less` is great for tailing logs, output, etc... and lets you search, filter, set marks.
> foreman start -c web=1,all_worker=3 > /tmp/x & less -r+F /tmp/x; kill -SIGINT %
I run this inside of screen so that I can decide not to wrap the lines.
Re:Rtail – Terminal output to the browser using Unix pipes
by aethr on Wednesday July 08, 2015 @01:45AM
(#9850007)
less is great, and I'm certainly comfortable using it (nice snippet btw!). Other devs on my team who are more web focused would probably find rtail easier to use.
We also have a Vagrant box for each project, and rtail would be trivial to add to the Vagrant template so that every development box has this running on a specific port without any setup or fiddling needed by each developer. At least that's the direction I'm thinking of going in right now, without having actually tried it out. :)
I would typically use standard debug logging and tail the output in a terminal while I test, but having that output in a browser, searchable, filterable by RegExp adds a whole additional layer of ease of use. Showing this to all the backend devs on my team today!