I got rick rolled :(. Probably an exploit in there.
I fixed this for the demo already :)
Rtail – Terminal output to the browser using Unix pipes
31–35 of 35 posts
Re: Rtail – Terminal output to the browser using Unix pipes
#32Earlier quoted context omitted.
I think there is. I keep getting redirected to a 10 hour rick roll youtube video
Ya loads http://bit.ly/1LRJuun that redirects to https://www.youtube.com/watch?v=BROWqjuTM0g&insecure_code=tr... 42["line",{"timestamp":1436363693619,"streamid":"rtail.org","host":"176.199.140.33","port":50049,"content":" window.top.location.href=\" ","type":"string"}" rel="nofollow">http://bit.ly/1LRJuun\" ","type":"string"} ]
I fix this for the demo already :)
Re: Rtail – Terminal output to the browser using Unix pipes
#33Earlier quoted context omitted.
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.
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'…
+1 for a common tool chain. It's really nice when you don't have to spend 1/2 the day figuring out someone's setup to help them fix a bug.
Re: Rtail – Terminal output to the browser using Unix pipes
#34Nicely done - the design is amazing. I had to solve a similar problem a while ago and wrote tailon:
https://github.com/gvalkov/tailon
Re: Rtail – Terminal output to the browser using Unix pipes
#35Wow! This is really cool! I would love to use this at my workplace. I had a small problem, though: it seems the clients don't keep very much data. For example, I filtered based on an expression that matched about 1-2 lines per second. The lines appeared, but disappeared almost as quickly. I suspect there is some small client-side buffer that I'm overrunning almost instantly; the log stream I used produces about 500 l…
Yeah, so the filter uses the internal buffer which is 100 lines. you can easily hack it to make it bigger (there is a closed github issue to look at for instructions). I don't want to make bigger buffers available just yet. I want to rewrite the webapp using ng2 and use an infinite scroll for the lines view. Feel free to open a new issue if you want!