Cli

If your Team, Organization or Company is serious about where to keep credentials used by services (or to interact with them), they are likely in Kubernetes Secrets, Hashicorp Vault, one of the various cloud-based Secrets Managers, 1Password, etc. Then, when running locally, they might be in your Environment Variables, in a .env, in a file or just in plaintext in a script (naughty!). This might lead to services and tools written to deal with those different “secret provision scenarios”. Or tricky/brittle local setups. ...

Fancy $PS1 setting The code to make the Bash prompt looks like mine is (~/.bashrc): 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 case $TERM in xterm*|rxvt*) TITLEBAR='\[\033]0;\u@\h:\w\007\]' ;; *) TITLEBAR="" ;; esac; PS1="${TITLEBAR}\n\[\033[0;0m\][\033[0;32m\]time: \ \[\033[0m\]\[\033[1;31m\]\t\[\033[0m\]\[\033[0;0m\]]-\ [\[\033[0m\]\[\033[0;32m\]host: \[\033[0m\]\ \[\033[1;31m\]\h\[\033[0m\]\[\033[0;0m\]]-\ [\[\033[0m\]\[\033[0;32m\]user: \[\033[0m\]\[\033[1;31m\]\u\ \[\033[0m\]\[\033[0;0m\]]-[\[\033[0m\]\[\033[0;32m\]bash: \ \[\033[0m\]\[\033[1;31m\]\v\[\033[0;0m\]]\n\ \[\033[0;0m\][\[\033[0;32m\]cwd: \[\033[0m\]\[\033[1;31m\]\w\ \[\033[0m\]\[\033[0;0m\]]# " Thanks to Bash Prompt HOWTO.