I just rebooted my server by accident because I wanted to play Space Engineers.

Long story short, dual booting. Needed to boot into windows. Typed reboot into my terminal. My terminal was not local. When am I finally getting around to set up my terminal color as red when it is connected to another host?

But two things are good here. This was my own server.. Well, bunch of stuff is running on it, including for my bachelor's thesis. But if that was a server of my company, that would have been worse.

Second thing, my systems are fault tolerant. I reboot once per week at the latest and for systems with fail overs once per day. I know they are coming back up. I don't worry. My Gitlab will be back in 5 minutes at the latest. I am going to reboot and play Space Engineers now.

Reboot your servers guys. Only way to make sure they'll survive reboots!

Just a quick follow up. I told you guys after rebooting my server by accident, I'll color in the terminals for my ssh connections.

Normal terminal in white. With the code to do it. Just a shell script with the name ssh earlier in the path than the actual ssh. That was the only solution that didn't fuck my auto-completion. compdef was somehow useless. But it is simple.

For some reason I had to hardcode the return color to white. Alacritty was not happy with just a no-color code. But whatever. Super useful. I won't accidentally restart non-host computers now.

Planning on extending this to have different colors according to the host. Like my homelab could be green. Live servers would be red. Dev servers blue. But that's for the future.

Just wanted to share my little improvement that will make my computing saver.