HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
cockpit-project
cockpit
Python2014–2026
cockpit-project / cockpit

cockpit

Cockpit is a web-based graphical interface for servers.

Web DevelopmentSystems & Infrastructure
Explore on GitHubRead Hacker News discussions
11Distinct people
12Mentions
0Explicit recommenders
15.4KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Cockpit is a web-based graphical interface for servers.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year12 dated mentions

Observed mentions: 2014-02-13 06:16:40 UTC to 2026-03-22 21:15:27 UTC.

0122014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20142015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC101
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC000
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC101
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC202
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC110
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC211
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC000
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC211

What Hacker News says

12 sources
kayson·Jun 6, 2022
See also: * homer - https://github.com/bastienwirtz/homer * heimdall - https://github.com/linuxserver/Heimdall * dashmachine - https://github.com/rmountjoy92/DashMachine * flame - https://github.com/pawelmalak/flame In a slightly different vein: * netdata - https://github.com/netdata/netdata * cockpit - https://github.com/cockpit-project/cockpit/ And then of course there's grafana which is definitely not for the feint of heart. There are so many page-of-bookmarks style dashboards, but if I'm being honest, none of them are all that great. Of the above, I like heimdall the best for its cleanliness and simplicity, but its hardly customizable. I think we'd be much better served by a really well thought-out framework for self-hosted/homelab dashboards with excellent API documentation that has pluggable modules for things like authentication, d
Read the rest
ata sources (e.g. docker, db, config file, service APIs), and the front end. This would allow people to easily build the dashboard with the features they want, and make it even easier for people to contribute a variety of "themes" for endless customization of how things are displayed.
In Dashy – A self-hosted homepage for your homelab
cmurf·May 14, 2019
I've been using Fedora Server for this, for several years. There is no GUI front end for configuring Samba, so it does take a bit of time and hassle to learn enough about Samba to edit the sample smb.conf.example the package comes with. This suggests a GUI is coming, not sure how it will be supported. I'd hope they'd make it possible to wrap that up as a Cockpit plugin. Cockpit is very cool, and is standard with Fedora Server. https://www.samba.org/samba/GUI/ https://github.com/cockpit-project/cockpit/issues/3534
In Over 25k Linksys routers vulnerable to sensitive information disclosure flaw
evol262·Feb 23, 2018
Yes, cockpit uses hostnamed and timedated. Plus journalctl, which I noted. I'm perfectly aware of how dbus works, and if you think that hostnamed or timedated have 'idiosyncractic' APIs, I'd challenge you to look at the API for glib. But it uses these because they are readily available over dbus. Not because cockpit has a hard dependency on systemd. While that functionality wouldn't work, it would be really trivial to write your own using cockpit.spawn() to call `date`... or `hostname ...` instead of hostnamed or timedated. The truth is that hostnamed and timedated are simply better than the CLI tools. However, I'm sure the Cockpit team would welcome a patch. More to the point, there is absolutely nothing in Cockpit which is explicitly using systemd APIs outside of dbus, and this would not be hard to work around. I know it's cool on HN to
Read the rest
hate on systemd, but this is dumb. Cockpit already uses bare `hostname`: https://github.com/cockpit-project/cockpit/blob/dbd7f3a8487a... It would be a 20 line patch to break the systemd "dependency" on hostnamed. This is not a project intrinsically linked to systemd. Even your hardwired "example" of journalctl is literally calling a process, which could just as easily be "cat /var/log/messages". It's 'hardwired' because systemd is the standard these days, whether you like it or not. However, extending the promise to simply do that if journalctl fails is trivial. Maybe your idea of 'hard' dependencies and mine are very different. To me, a 'dependency' on, say, Python, means that there are Python calls all over the place which a reliance on specific semantics. That means that stubbing it out for Ruby or Lua or whatever would be hard. It is not "we wrote our application with this in mind, but we could patch it into stubbable modules in 3 minutes".
In Cockpit – Administer Linux servers via a web browser
JdeBP·Feb 23, 2018
That is directly contradicted by Cockpit's own doco, which explicitly states that Cockpit uses the systemd APIs and that "use of alternate system APIs are not currently implemented". * http://cockpit-project.org/guide/latest/feature-systemd.html It should of course be obvious that Cockpit does explicitly deal with systemd. Desktop Bus is a transport layer, and the important thing about it is what DBus servers are on the other side of the broker are being talked to. In the case of Cockpit they are things like systemd's own idiosyncratic API for process #1 ... * https://github.com/cockpit-project/cockpit/blob/0dd4ee7bac14... ... systemd's hostnamed server ... * https://github.com/cockpit-project/cockpit/blob/0dd4ee7bac14... * https://www.freedesktop.org/wiki/Software/systemd/hostnamed/ ... and systemd's timedated server. * https://github.
Read the rest
com/cockpit-project/cockpit/blob/dbd7f3a8487a... * https://www.freedesktop.org/wiki/Software/systemd/timedated/ Cockpit also hardwires use of systemd's journalctl program. * http://cockpit-project.org/guide/latest/feature-journal.html * https://github.com/cockpit-project/cockpit/blob/0dd4ee7bac14...
In Cockpit – Administer Linux servers via a web browser
cmurf·Sep 19, 2016
Substitute blivet-gui for gparted. It groks pretty much all Linux storage: MBR, GPT, mdadm and LVM raid, Btrfs, LUKS. https://github.com/rhinstaller/blivet-gui http://www-rhstorage.rhcloud.com/blog/vtrefny/blivet-gui-20 Not just for servers, but quite useful on them is Cockpit which leverages storaged and libblockdev, providing a good chunk of storage configuration via web UI, among other things. https://github.com/cockpit-project/cockpit
In The Linux graphics stack from X to Wayland (2011)
antoncohen·Feb 13, 2014
Mind blown. I thought this was some ordinary Python or Ruby app. It reminded me of Ajenti (http://ajenti.org/), which is nice admin panel. But Cockpit is insane (not in a bad way). [starting cockpit] will cause systemd to listen on port 21064 and start cockpit-ws when someone connects to it. Cockpit-ws will in turn activate cockpitd via D-Bus when someone logs in successfully. Cockpit is written in C, by Red Hat. The web frontend has dbus.js that does D-Bus over WebSockets to communicate to the backend. I expect this project will evolve into something much bigger. https://github.com/cockpit-project/cockpit
In Cockpit, a web-based server management interface

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.