Hello all,
I would like to use cockpit as and update manager for all my linux machines.
My question is if i can only install this component, and if so how can i do it,
I don't want to install the "full" cockpit version on some machines, because some of them already have web servers and such, and that's pretty much the reason why I want to install only the update module.
Regards,
Hello Carlos,
carlos castro [2021-09-20 8:38 +0100]:
I would like to use cockpit as and update manager for all my linux machines.
My question is if i can only install this component, and if so how can i do it,
The minimum packages that you can install are cockpit-packagekit for the "Software Updates" page, and cockpit-system to get the "shell". The latter has a lot of other pages, though. You can add "override files" to /usr/share/cockpit/ or ~user/.local/share/cockpit to hide pages though, if you desire: https://cockpit-project.org/guide/latest/packages.html#package-manifest
If you want to use https://target.machine:9090 directly, you also need cockpit-ws (the web server). Otherwise, install that on just one central machine and use the "remote hosts" facility (on the login page or the host switcher in a Cockpit session), then ssh suffices on the remote machines. This is what I'd recommend for managing many machines, to avoid having lots of web servers.
Martin
Hello,
Thanks for the awnser.
That's what I pretend. To install just the web in one server and manage all updates from that server without the need to install the full package in all the other servers.
I'll try do the procedure you pointed.
Maybe it could be a good feature during the install to ask what 'plugins/parts' you would like to install.
Regards,
A quarta, 22 de set de 2021, 09:51, Martin Pitt martin@piware.de escreveu:
Hello Carlos,
carlos castro [2021-09-20 8:38 +0100]:
I would like to use cockpit as and update manager for all my linux
machines.
My question is if i can only install this component, and if so how can i
do it,
The minimum packages that you can install are cockpit-packagekit for the "Software Updates" page, and cockpit-system to get the "shell". The latter has a lot of other pages, though. You can add "override files" to /usr/share/cockpit/ or ~user/.local/share/cockpit to hide pages though, if you desire: https://cockpit-project.org/guide/latest/packages.html#package-manifest
If you want to use https://target.machine:9090 directly, you also need cockpit-ws (the web server). Otherwise, install that on just one central machine and use the "remote hosts" facility (on the login page or the host switcher in a Cockpit session), then ssh suffices on the remote machines. This is what I'd recommend for managing many machines, to avoid having lots of web servers.
Martin _______________________________________________ cockpit-devel mailing list -- cockpit-devel@lists.fedorahosted.org To unsubscribe send an email to cockpit-devel-leave@lists.fedorahosted.org 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/cockpit-devel@lists.fedorahoste... Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
cockpit-devel@lists.fedorahosted.org