tail CI logs over SSH
35 points by eti
35 points by eti
This is an example of what I've always called San Francisco coding (although the author is London based and their infra is in Stockholm). San Francisco coding is when you assume latency isn't significant.
tangled.org is 300ms away from me. Using an interactive UI over SSH with 300ms of latency is never going to be a good experience. You could geo-distribute your SSH endpoints, but the tail is probably wagging the dog at that point, and there will still be some amount of annoying UI latency for many of your users, especially those users on spotty connections.
The two founders of Tangled are in the UK and Finland, fyi. (Your point about latency around the world stands, just want to point out they're absolutely not SF or SV bros lol)
Yep, in fact it looks like tangled.org is hosted on UpCloud, an EU based cloud. The A record for tangled.org points to an IP in Stockholm.
AFAICT all the TUI does is switch between different tabs (files), so latency isn't that big of a problem, I assume most of the time you'd be looking at one of the files, and not constantly switch between them. Scrolling might be a bit of a problem if that is done remotely and not locally.
for gitlab users, the official glab cli tool allows for something similar. running
$ glab ci trace
… shows the status of the jobs in the pipeline of the current branch, and an interactive menu that lets you select a specific job. the output automagically updates (cf. tail -f) if the job is still running.
Love seeing ssh apps