Hello, I’m developing an application around Cockpit with my colleagues and I was wondering if there’s a way to consume Cockpit without our application being a plugin inside the Cockpit interface.
Our application is something like an HPC Cluster Manager, so it makes total sense to use Cockpit as the basis, there’s a lot of functionality built in, and the upstream development is just awesome. But as per consumer feedback it would be better to have a separate web interface instead of it being a plugin inside the Cockpit web interface. I’m looking through the documentation and there’s the Cockpit API: https://cockpit-project.org/guide/latest/development.html I see that Cockpit can be embedded entirely in an external application, but this is not what we really want to do. We want to do a new web interface, using IBM’s Carbon design guidelines with HPC in mind and not the system being managed, which is the vision of Cockpit as is. There’s this Deep Integration on the documentation and I think what we need is just this, but the documentation is lacking. The point is: as today, is it viable to consume Cockpit with its API’s in a totally different frontend interface? So I can use things like: authentication, performance graphs, dashboards, user creation, logging, console terminal, etc? Regards, _______________________________________________ cockpit-devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/[email protected]
