[Article proposal] Using Cockpit to graphically manage systems, without installing Cockpit on them!

Article Summary:
Cover how to use the recently introduced Cockpit functionality that allows you to manage remote systems without having Cockpit installed on them. Previously in order to use Cockpit to manage remote systems, there was a requirement that Cockpit was installed on them.

Article Description:
In this article I’ll cover an overview of what Cockpit is, and its use cases. From there, I’ll discuss a couple of the main objections I frequently hear to using Cockpit: 1) I don’t want to run the Cockpit web server on my systems, and 2) I don’t want to (or can’t) install additional packages on my systems. In regards to concern 1) I’ll discuss the various methods available to use Cockpit over SSH without using the Cockpit web server. For concern 2) I’ll cover the new Python bridge for Cockpit and how it can be used with the Cockpit Client Flatpak to manage remote systems that don’t have Cockpit packages installed.

Next, I’ll walk through how to install the Cockpit Client Flatpak on Fedora, and show an example of using it to connect to a Fedora server system that doesn’t have Cockpit packages installed. I’ll explain the prerequisites that are needed to use this functionality. The final section of the article will cover several frequently asked questions about this functionality.


Sounds good. +1.

@briansmith +1 from me as well.
I’ve created Pagure ticket #212 1 to track this article.

Please use comments on ticket #212 1 if you have questions or need to communicate with the editors about anything.

The overall work flow is described at this link as well as other helpful information.

When you have it ready to review in the Fedora Magazine WordPress site, please leave a comment in ticket #212, with a preview link, and we will start the review process.

Thanks for volunteering to write for the Fedora Magazine!

This topic was automatically closed after 180 days. New replies are no longer allowed.