3 ms·
Cockpit is super cool. I've been using it for personal stuff for years now, especially since it's trivial to enable and use. I even use it in production for m
by freedomben 6y ago
Cockpit is super cool. I've been using it for personal stuff for years now, especially since it's trivial to enable and use.
I even use it in production for monitoring small sites/apps. The graphs for CPU/Mem/Network/Disk are really great, and I can leave them open in a tab on my browser. I run one fairly popular blog that as a web machine and a db machine, and it's great for that.
That said I don't use it for "serious production" where I have more than a couple of machines simply because at that scale I prefer cattle to pets and I prefer aggregation.
I also find myself strongly preferring SSH and the CLI, likely because I'm very familiar with all that and have been doing that for decades.
I've never heard of security issues with Cockpit, but I do firewall it off from everyone but my own IP (or a few others if they are involved). It's pretty easy to do:
# Get your IP address from home or work: curl -s 'https://api.ipify.org'
MY_IP=<ip>
firewall-cmd --zone-public --permanent --remove-service=cockpit
firewall-cmd --zone=public --permanent \
--add-rich-rule="rule family=\"ipv4\" source address=\"${MY_IP}\" port protocol=\"tcp\" port=\"9090\" accept"
firewall-cmd --reload
Here's a gist of it: https://gist.github.com/FreedomBen/0aabe5493ba02d1c9bb33fea2ec5e944 https://gist.github.com/FreedomBen/0aabe5493ba02d1c9bb33fea2...