4 ms·
For tmux users: put something like this in your .tmux.conf on production servers: set -g window-style 'fg=red,bg=black' It will color the text red, hopefu
by throwaway8941 7y ago
For tmux users: put something like this in your .tmux.conf on production servers:
set -g window-style 'fg=red,bg=black'
It will color the text red, hopefully reminding you to be extra careful. Adjust according to your preferences.
One other "defensive scripting" trick I frequently use is starting any `rm` command with `ls`, double checking its output (or triple checking if it's a recursive one), and then replacing `ls` with `rm`. It barely takes any extra time if you're proficient with emacs-style readline hotkeys:
C-a M-d rm C-m
- KajMagnus 7y agoThat's nice — I usually start my commands with `# ` but then there's no tab completion. I'll try `ls`
- leni536 7y agoI usually use echo for the same purpose.
- gryfft 7y agoIn this vein, I set my PS1 to bold red capital letters on bastion hosts and alias sudo="echo 'You're on a jump box moron :p'" I do the tmux color trick too-- color coded by environment for each bastion.
- davedx 7y agoWe do this for our database connections in Azure Data Studio / the Windows version of it. Really great idea.
- PeterisP 7y agoSomething like this to obviously distinguish environments is good practice - at one company we implemented scripts for terminal color-coding like this after some downtime caused by a destructive backup restore accidentally being run in the production environment instead of an acceptance testing system, which was in all aspects identical to the production system. And I've seen a solution for more secure environments where physical separation was used with the operator having separate monitors/keyboards, and the "important" system having a different color keyboard and monitor frame.