It's nice because it's light on resources, using near nix when not actively queried (runs a passive web service that responds only when you need it) and provides an overview of performance and resource use and management tools across a LAN all my Llinux servers including Pis.
The conspicuous absence for the moment is the router/gateway and it would be nice to see it on the same interface. Cockpit project don't build an opkg. but there's no reason it can't be (runs fine on ARM boxes and is intended to be light on resource use).
I've had a look into it and there's some fine documentation on how to build opkgs:
Thanks, very interesting. Begs the question why OpenWRT doesn't keep its opkg up to date and relies on such an old tailored version (the age old risk of forking software). Are there specifc customisations that yocotproject didn't want to merge in? I'm sort of curious as I have a QNAP NAS that uses opkg as well (and heir own qpkg as it happens).