34 ms·
I set it up for my handrolled homelab server automation ( all Arch Linux servers ), back when I was doing everything with virsh. It worked "ok". It required pu
by Naac 6y ago
I set it up for my handrolled homelab server automation ( all Arch Linux servers ), back when I was doing everything with virsh.
It worked "ok". It required pulling in a bunch of dependencies I wouldn't have normally installed. I had it set up behind an HAproxy LB, with ssl terminated at the LB. When I was using it ~1 year ago, it was pretty buggy, and certain components would crash and I would have to restart the web page.
Overall it was a mediocre experience, but I suppose better than having to ssh into every server. The main pain point was that I still had to go in to every server, and install cockpit.
In the end, I ended up just moving on to Proxmox. But I suppose cockpit is nice if you don't want a centrally managed cluster, but still want a web interface.
- warmwaffles 6y agoGlad I am not the only insane person running Arch for their homelab stuff.
- deleted 6y ago[deleted]
- circularfoyers 6y agoConsidering Cockpit is neither supported nor tested on Arch Linux[1], I think forming an opinion of it based on that would be unfair. [1] https://cockpit-project.org/running.html https://cockpit-project.org/running.html
- Naac 6y agoIt's in the official Arch Linux repository. And they even decided to include it in their table from your link. I think its definitely a valid opinion to have. And I would stand by not recommending Cockpit until it becomes more polished.