New incremental update to Exosphere, my simple CLI and TUI driven patch reporting application for remote UNIX systems.
Improved vuln.xml handling in the FreeBSD provider, and clearer sudo error messages that point you to the documentation.
https://github.com/mrdaemon/exosphere/releases/tag/v2.4.0
#exosphere #linux #unix #openbsd #freebsd #homelab #SRE #python
Neat, so it turns out the previous groundwork I laid out in supporting repository source parsing in the FreeBSD provider for Exosphere just immediately paid off and PkgBase enabled systems just work out of the box. System updates are just listed very explicitly in there.
I was worried I'd need to expand it but no, it just works, so that's cool.
Small maintenance release of Exosphere, my patch reporting program for remote UNIX systems.
A single minor fix to json reports, but also a ton of small improvements to the documentation.
If you'd like to have a neat CLI and pretty TUI to manage updates on a bunch of unix-like systems over SSH, do check it out
https://github.com/mrdaemon/exosphere/releases/tag/v2.3.0
#exosphere #linux #unix #openbsd #freebsd #homelab #SRE #python
I've released version 2.2.0 of Exosphere, my patch reporting program for remote UNIX systems.
It contains support for SSH connection pipelining, with associated tools to manage their state, as well as an exhaustive polish pass.
Multiple internal systems have been refactored to be much cleaner and easier to maintain.
https://github.com/mrdaemon/exosphere/releases/tag/v2.2.0
#exosphere #linux #unix #FreeBSD #OpenBSD #HomeLab #SRE #Python
I keep forgetting how rewarding it is to finish a core feature of something and then making a small bit of UI or command that shows the state of it.
You get to have a Nice Visual for your hard work and see it going somehow.
I've been adding some form of SSH pipelining to Exosphere, my patch reporting program for remote unix systems.
The idea was that I could just remove connection lifecycle handling entirely from package manager providers and setup/discovery code, and manage that from within the task runners.
So I added an opt in config toggle that will leave connections open and reap them via a background thread if they have been idling for more than X amount of time. That way chaining operations takes significantly less time, since the connection gets reused.
This is basic, a bit naive, but it works without issues in my weeks spent using that code myself on 21 hosts with no ill effects.
I'm just at the stage where I have to convince myself it's Good Enough, Actually(tm) because it's making my Race Condition sense tingle (even though there's really no risk in context) and I'm this close to wrapping connection semantics in RLocks for no reason other than to make the feeling go away.
Just released a Big Quality of Life update to my patch reporting program for remote UNIX systems.
Inventory filtering, Themes support, massively improved tab completion in interactive mode and more!
https://github.com/mrdaemon/exosphere/releases/tag/v2.1.0
#exosphere #linux #unix #FreeBSD #OpenBSD #HomeLab #SRE #Python
The problem with using software you wrote yourself is that you impulsively add features you feel would improve your life, and then get annoyed at how other parts of the software don't have the same feature.
So I guess I'm adding filtering capabilities to the Inventory view in Exosphere now
Finally released version 1.5.0 of my update reporting program for remote unix systems.
It now has reporting! It can output nice document based reports in HTML, Markdown, Text and JSON
The JSON part is ideal if you want to integrate Exosphere into anything else.
Documenting things concisely is hard sometimes.
I swear I finished the Reporting feature in Exosphere over two weeks ago, but I've been rewriting the documentation for it like 20 times. There's a lot of stuff and it was supremely annoying to present in a way that doesn't look nasty or isn't overwhelming.
If of course resulted in me writing two more questionably useful custom Sphinx extensions just to get it done, but I think I'm pleased with the results.
It finally just needs a few editing passes to reword some stuff and make sure I don't publish 1.5.0 with embarrassing typos or shitty grammar that makes me question my command of English, but the biggest hurdle has been passed I think.
mr_daemon
