Live data from Hacker News

Cockpit: Web-based graphical interface for servers

cockpit-project.org

71–80 of 199 posts

Re: Cockpit: Web-based graphical interface for servers

#71
post #18
post #17

Earlier quoted context omitted.

I was curious because my gut says ideology about the vastness of systemd. Turns out, there's still a number of systems that don't make use of systemd: https://en.m.wikipedia.org/wiki/Category:Linux_distributions... They may have more nuanced answers.

Sure. I used to be one of the ideological ones using Devuan. "A number" being the operative word here. It's a small number, and for a pretty good reason. I get there is an important reason to have choice, but bragging about how you don't use systemd is just meme-y and comes from a place of (misplaced) elitism usually.

>I get there is an important reason to have choice, but bragging about how you don't use systemd is just meme-y and comes from a place of (misplaced) elitism usually.

I think you're projecting. No one bragged about such a thing, they just merely mentioned their specific situation.

It's not all text-editor-wars and squabbles, as stated and even acknowledged before : there exist reasons aside from nerd elitism to choose something other than systemd.

Re: Cockpit: Web-based graphical interface for servers

#72

Love it-- but since I'm not using systemd, it's a no-go. Would love to see it support more diverse systems, but last I checked it's pretty tightly coupled and I'm not sure who would have the bandwidth to adapt it.

The reason cockpit exists is systemd and dbus. Without them it would be much harder to develop.

That's true to some extent, but I think the real reason for the coupling is because that's just IBM's use-case and worldview. Cockpit is essentialy a wrapper over systemd commands, and one commentor has demonstrated how it could have been envisioned as a modular platform allowing end-users to wrap anything from direct kernel interfaces to entirely custom commands. They've made something useful and beautiful, but I wish it had been designed to make less assumption about it's runtime environment and expose it's toolkit to end-users so that we could all enjoy it for our own needs.

Re: Cockpit: Web-based graphical interface for servers

#73
post #19

Love it-- but since I'm not using systemd, it's a no-go. Would love to see it support more diverse systems, but last I checked it's pretty tightly coupled and I'm not sure who would have the bandwidth to adapt it.

It can be hosted without Systemd: sudo runuser -u cockpit-wsinstance -- /usr/libexec/cockpit-ws --port=9090 --for-tls-proxy

Thanks! Funnily enough, I don't think this matches the approach I tried from some GH issue back in the day :p

And of course, we'd still need to reimplement many of the existing systemd-based modules. I wonder if the creation and maintenance of these modules (given the existing size and status of the ecosystem) is less-than-trivial in comparison to something like a set of NixOS config bindings. At the end of the day, I'd be more exited about a project that puts portability and customization first than retrofitting an upstream product to whom I'm not a target user.

Re: Cockpit: Web-based graphical interface for servers

#74
post #37

Earlier quoted context omitted.

This is definitely not it. There were enterprise and community editions and I was stuck at 15.

Perhaps you mean https://openitcockpit.io/editions/ ?

No, I'm not crazy. Just checked.

Re: Cockpit: Web-based graphical interface for servers

#75
post #65

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…

> It's for people who want to point and click, can't do a bash for/while loop, don't understand pipe chaining commands, and don't like using vim "Instagram filters are for people who don't know how to work with Photoshop layers, don't understand basic color blending operations, and who just want to swipe." I mean, yes.

I have no problem viewing pictures shared by those who don't understand basic color blending and just want to swipe.

But I may have a problem with people who can't do a bash for/while loop or understand pipe chaining commands be responsible for administrating my company servers.

I don't see how the comparison between adminstrating servers and sharing pictures on social media is a useful comparison.

Re: Cockpit: Web-based graphical interface for servers

#76

Earlier quoted context omitted.

Terminal emulators, which can run SSH clients, are absolutely possible on a mobile device. https://termux.dev/en/

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.

Re: Cockpit: Web-based graphical interface for servers

#77
post #75
post #65

Earlier quoted context omitted.

> It's for people who want to point and click, can't do a bash for/while loop, don't understand pipe chaining commands, and don't like using vim "Instagram filters are for people who don't know how to work with Photoshop layers, don't understand basic color blending operations, and who just want to swipe." I mean, yes.

I have no problem viewing pictures shared by those who don't understand basic color blending and just want to swipe. But I may have a problem with people who can't do a bash for/while loop or understand pipe chaining commands be responsible for administrating my company servers. I don't see how the comparison between adminstrating servers and sharing pictures on social media is a useful comparison.

I don’t understand why you think the fact that someone may choose to point and click to do something, a task which depending on the UI can be completely mindless and yet significantly safer eliminating any chance of making a mistake (by throwing in a typo for instance), does not know what a bash for/while loop is?

I suspect most people here used the HN web interface to post their comments, even though constructing an HTPP request to send to HN using curl to post your comment wouldn’t be significantly harder. The fact that they used the point and click HM Web UI doesn’t mean they’re incapable of constructing such a request where it actually is needed.

Re: Cockpit: Web-based graphical interface for servers

#78
post #75
post #65

Earlier quoted context omitted.

> It's for people who want to point and click, can't do a bash for/while loop, don't understand pipe chaining commands, and don't like using vim "Instagram filters are for people who don't know how to work with Photoshop layers, don't understand basic color blending operations, and who just want to swipe." I mean, yes.

I have no problem viewing pictures shared by those who don't understand basic color blending and just want to swipe. But I may have a problem with people who can't do a bash for/while loop or understand pipe chaining commands be responsible for administrating my company servers. I don't see how the comparison between adminstrating servers and sharing pictures on social media is a useful comparison.

What if they CAN do a bash for/while loop, but they prefer not to because bash is the ugliest effing language they've ever seen

Re: Cockpit: Web-based graphical interface for servers

#80
post #75

Earlier quoted context omitted.

I have no problem viewing pictures shared by those who don't understand basic color blending and just want to swipe. But I may have a problem with people who can't do a bash for/while loop or understand pipe chaining commands be responsible for administrating my company servers. I don't see how the comparison between adminstrating servers and sharing pictures on social media is a useful comparison.

I don’t understand why you think the fact that someone may choose to point and click to do something, a task which depending on the UI can be completely mindless and yet significantly safer eliminating any chance of making a mistake (by throwing in a typo for instance), does not know what a bash for/while loop is? I suspect most people here used the HN web interface to post their comments, even though constructing an…

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