squeeb@quokk.au 2 weeks ago
On face value it doesn’t look too different to dockcheck. What you’ve described (CLI, read-only, no auto updates, sends notifications via channel of your choosing) sounds exactly like how my dockcheck is set up
squeeb@quokk.au 2 weeks ago
On face value it doesn’t look too different to dockcheck. What you’ve described (CLI, read-only, no auto updates, sends notifications via channel of your choosing) sounds exactly like how my dockcheck is set up
BlackRaincoat@lemmy.world 2 weeks ago
Honestly, no — I hadn’t come across dockcheck before now, so thanks for pointing it out. I didn’t do a big survey of what’s out there; I just had an itch (notify-only update checks across a few hosts, with a proxy, no auto-updating) and nothing I’d tried quite fit how I wanted it, so I ended up writing my own. Sounds like dockcheck lands in a similar space — I’ll take a look at how it does things. Not trying to claim mine’s better; different paths to the same problem.
squeeb@quokk.au 2 weeks ago
Maybe you’ll find dockcheck is a more mature and rounded version of what you wanted, and you can fork it to tinker with the other features you want for your own personal use if it doesn’t do everything you wanted! Or maybe you’ll find you like yours better anyway. Hope you find something interesting in it, regardless!
I personally find dockcheck on each host + a simple systemd service is more or less perfect for my needs. I hook it up to a grafana dashboard so it can give me a running tally of what’s out of date and what’s not alongside the rest of my monitoring stack.
BlackRaincoat@lemmy.world 2 weeks ago
Thanks, that’s a genuinely nice way to look at it. The grafana tally is a cool setup - piping update status into the rest of your monitoring makes a lot of sense. I’ll definitely poke at dockcheck to see how it does things. Cheers!