Hello Bernd,
Bernd Wechner [2020-05-14 7:34 -0000]:
That set does include an OpenWRT router and a QNAP NAS, both of which
are smaller stripped down embedded Linux systems if you will which use the opkg package
manager:
https://en.wikipedia.org/wiki/Opkg
There are no cockpit opkgs available that are known to me, so on that platform
you'd probably need to build yourself. I assume that there's some development
environment that cross-compiles to OpenWRT, as one surely doesn't want to build
software *on* the router itself :)
These systems have web interfaces already (OPenWRT typically under
lighttpd and QNAP use Apache) but methinks cockpit is independent of these running
it's own web service (cockpit-ws).
That's correct. It needs to have cockpit-ws, as it's more than "just" a
HTTP
server. The main work happens through a websocket.
Like the Pi these are typically ARM based machines and it's even
plausible that the Pi build runs on them, but they don't typically have developement
tools on them by default for building (compiling and linking) software locally.
Yes, the Raspbian/Debian/Ubuntu armhf/arm64 packages should work just fine on a
Pi. We don't test the page functionality on a Pi, though -- i. e. usually one
doesn't run NetworkManager or storaged on a Pi (unless it's actually configured
as a desktop), and there's no VMs either, so some pages probably won't be that
useful. But Overview, Logs, Services, Terminal, performance graphs etc. should
all be fine.
Martin