Fun trip down memory lane. Also, bitchin’ domain name!
I’ve already got my copy of the book and have even started reading it! Good on ya, and good luck!
Also, when you start hosting more than 2-3 services, keeping them up-to-date might become a hassle which you can forget. For docker-based hosting I’d recommend you setup watchtower, which can keep your servives up-to-date for you.
I would caution against automatic updates! Notifications, yes absolutely. But automatically updating things is a great way to have things break suddenly when you’re not in a good place to troubleshoot.
I would enjoy training a LLM on my aggregated command history and using that for auto completion, or maybe using an open source one trained on a larger set from the community, but I am very uncomfortable sending data about every command (as I’m writing it!) to any company.
This might be a little more than you’re asking for, but I would recommend something like Node-RED with a feedparser. Reason being: it opens up a lot of options and could be a useful tool for things other than this one use case.
I last used it seriously like 7 or 8 years ago and it was fine. I put it on par with GitHub at the time. The ability to self host for free without too much trouble also really affected my position on it.
I haven’t really enjoyed the few times I’ve had to use it in the last couple of years, though.
Wait, that’s like C with
extrafewer steps