There is one implementation detail that I geek out about:
It is zero config and has built-in leader nomination for running the web server and MCP server. When you start one `teemux` instance, it starts web server, .. when you start second and third instances, they join the first server and start merging logs. If you were to kill the first instance, a new leader is nominated. This design allows to seamless add/remove nodes that share logs (a process that historically would have taken a central log aggregator).
A super quick demo:
npx teemux -- curl -N https://teemux.com/random-logs
zareith•1h ago
gajus•1h ago
tee (Unix command that splits output) + mux (multiplexer) = teemux
cap11235•56m ago
gajus•56m ago