But Cockpit is insane (not in a bad way).
[starting cockpit] will cause systemd to listen on port 21064
and start cockpit-ws when someone connects to it.
Cockpit-ws will in turn activate cockpitd via D-Bus when
someone logs in successfully.
Cockpit is written in C, by Red Hat. The web frontend has dbus.js that does D-Bus over WebSockets to communicate to the backend. I expect this project will evolve into something much bigger.I was looking at the code and was surprised to find only Javascript and C, but your quick summary on the implementation makes me want to watch from the sidelines, cautiously.
That said, very interesting project AFAICT.
I'm not looking for a a monolithic solution, but something in which I can integrate all of our current scripts, third party tools, semi-manual processes and what have you.
In the real world, server management is a mix of tons of little tools and procedures, usually run over SSH.
However, handing SSH access to our systems to a third party SaaS tools scares the crap out of me.
You're not alone. It's one of the reasons I'm a bit sad that open-source development of commando.io ceased in favour of their SaaS version.
(Sorry. I understand if you mod me down for this. :P)
> Cockpit is under heavy development and it's advised you only run it in a virtual machine for now.
Another interesting Red Hat backed project in the same field of server management and deployment is The Foreman http://theforeman.org/manuals/1.4/index.html