Live data from Hacker News

Cockpit: Web-based graphical interface for servers

cockpit-project.org

101–110 of 199 posts

Re: Cockpit: Web-based graphical interface for servers

#101
post #79

Why use this when Webmin has done the job for decades? https://webmin.com/

A possible reason: if you're already a RHEL shop, you're happy with your RHEL support contract and you train up all your folks to be RHCE, then Cockpit is the "supported" web admin tool.

Second: webmin also has a patchy security history. I don't know enough about cockpit to say it's any better but it would certainly be enough of an issue to review all of the options.

Re: Cockpit: Web-based graphical interface for servers

#102
post #87

Earlier quoted context omitted.

I think there's an elitism within the Linux world to being a totally CLI user

There does seem to be a bit of it yes, but I thought it had become less common. Reminds me of a colleague I met once who was happily boasting he's a 'real' HTML developer because he writes everything in Microsoft notepad. I took a look at his work and cried inside - broken tags, bad formatting and of course he didn't escape all his characters correctly. Being able to type some characters on a keyboard does not make a…

> Being able to type some characters on a keyboard does not make anyone superior to a user that uses a point+click interface.

There isn’t a causal relationship, but the two are heavily correlated. Getting deep into the details of most server software means doing so via CLI, because the people who built the software intended it to be used there, since servers are usually headless.

Even if you run a DE, chances are high you’ll still end up editing some config files in a text editor, and running commands in a terminal emulator.

It’s a bit like [n]vi[m] - learning its esoteric commands doesn’t make you good at coding or ops, but there’s a decent chance you wouldn’t bother to spend the time learning it unless you needed the speed increases it grants you.

Re: Cockpit: Web-based graphical interface for servers

#105

I'm an actual RHCE. This thread has to be some big Red Hatter click farm or something. The artificial positivity is striking. Is Red Hat threatening to pull funding for this project or something? Just weird. Cockpit is okay but it's basically Red Hat's equivalent to the Windows Server Manager tool, and I have no doubt it was directly inspired by Server Manager. It's development and improvement over the years has been…

I've been using it because we deliver application servers based on Red Hat / CentOS to customers that are unfamiliar with Linux. 99% of the time, they do not need to log in to the command-line for anything. When they do, Cockpit has been a lot easier for them to understand than navigating ssh and bash.

Re: Cockpit: Web-based graphical interface for servers

#106
post #36

The cool thing about this project is that as it uses systemd's socket activation, it requires no server processes at all. There is no waste of resources when Cockpit is not being used. Accessing a page is literally the same as invoking a command-line tool (and quitting it). No more, no less. What a beautiful design.

Interesting, I always thought socket activation meant defer launching a process until somebody tries to access it through the network, but... does it also finish the web server process (or whatever is used here) as well after the request is serviced?

Re: Cockpit: Web-based graphical interface for servers

#107
People who decry graphical admin interfaces in favor of command line are missing the wood for the trees.

Sure, clickops is no way to run a server - but neither, if we’re honest, is ssh.

For a working machine, server state should be reproducible from scratch. Install an OS, add software, apply configuration, leave well alone. If you’re going in with ssh or cockpit you’re just going to screw something up.

So the only reason you should be working on a server directly is because you’re doing something exploratory. And in that case gui vs command line isn’t as clearcut as people want to make it. GUIs emphasize discoverability and visibility which can be helpful in that experimental phase when you’re trying to figure out how to get something set up right.

Re: Cockpit: Web-based graphical interface for servers

#109

Earlier quoted context omitted.

> Lol! Are you ready to deploy an ssh-capable terminal emulator at all times? What terminal emulator isn't ssh-capable? Where would you not be able to open a terminal emulator? I am so confused. > What's wrong with making simple tasks simple? The limited tasks exposed by cockpit are also simple (or depending on the individual, simpler) in a terminal, but if you want a point-and-click UI for just a few things, go ahea…

> Where would you not be able to open a terminal emulator? I am so confused. A mobile device. I don't use terminal emulators without access to some non-touch keyboard so I want a simple interface on my mobile device. > That cockpit is very limited and seemingly has no future does not mean you can't like what it does now. Just might be worth considering if there are better-supported alternatives. Sure then compare coc…

> A mobile device. I don't use terminal emulators without access to some non-touch keyboard so I want a simple interface on my mobile device.

Whether you want to use a terminal emulator on your phone doesn't change whether it's available.

I wouldn't want to use a clumsy web app with dangerous buttons that put me a single mis-touch on a poorly thought out touch target away from messing up/rebooting/powering down a server from my phone either, but that doesn't change that cockpit is available.

> Sure then compare cockpit with other webmin-esque tools, not a terminal emulator.

You compare it to the options available, which includes both terminals and webmin equivalents.

I don't know if there's much of a space left for cockpit or webmin equivalents though. There's hypervisors with dedicated UIs like Proxmox and oVirt, but that's not the same.

Re: Cockpit: Web-based graphical interface for servers

#110
post #76

Earlier quoted context omitted.

I know. Android is a capable platform. I'm just not going to use it on a mobile device without a keyboard, sorry.

There are countless terminal emulators for iOS that support ssh. Termius, prompt, and blink off the top of my head.

And using any of them is more of a hassle than just using cockpit instead.
Post reply on HN