Hacker News Reader

Comment by jnsaff2 | Hacker News Reader

This is how I felt when a Gitlab employee deleted the production database by doing it in the wrong terminal window.

Get into the habit of colour-coding your important SSH sessions, red/green/blue can give you a very powerful subconscious check before doing something very silly.

How do you do this so that it lasts? I find mine resets to default

Can’t you set it in the .zshrc file?

I use iTerm2 and have different profiles for different directories/remote hosts. iTerm switches the background colour automatically for me. I'm sure other terminal emulators would have similar features.

https://bsago.me/tech-notes/change-ssh-background-colour-wit....

what phist wrote. Color code the backgrounds of your servers, different colors. So anyone who connects to 'take console' in any system is hit by a blinding electric Green/Blue/Red/Yellow and other striking colors.

I assume that all systems already have descriptive names App_DEV_Server1, App_PROD_Server5, etc.

It also helps if (ofc they would be right??) in separate IP groups/WLANS?

If you are running Windows, it's a good idea to use BGINFO.exe by SysInternals (or Winternals as we old people still call it), and display the most relevant info (showing Dev/Prod/UAT/etc.) with big-big-big letters.

Post mortem for the outage I referred to.

https://about.gitlab.com/blog/2017/02/10/postmortem-of-datab...

Why do employees have write access to production DB?

Lazy attitude towards proper role management and poor engineering practices. More common in small companies or small teams managing their own service (db and app)

Really all you need is logging and potentially temporary read access to the db if you need some info that you can't derive from the logs.

Reply on news.ycombinator.com