same config as insp, easier to add changes for all computers

1 files changed, 48 insertions, 0 deletions

diff --git a/home/xyz/.ssh/config b/home/xyz/.ssh/config
index 88b45f7a..1fec70fb 100644
--- a/home/xyz/.ssh/config
+++ b/home/xyz/.ssh/config
@@ -2,7 +2,55 @@
 # another approach is to put it under `HOST *`
 # https://unix.stackexchange.com/a/577490/459013
 AddKeysToAgent yes
+# If use alacritty, need send COLORTERM env to remote server to let remote server ls show color,
+# more see alacritty.toml config
+SendEnv COLORTERM
+
+# tabs and empty only for readability, without also works, not sure about newline
+Host studio
+	Hostname flylightning.xyz
+	Port ssh-isp
+	User xyz
+
+Host insp
+	Hostname xyzinsp
+	User xyz
+
+Host pp
+	Hostname xyzpp
+	User xyz
+
+Host qw
+	Hostname localhost
+	Port qemu-win-ssh
+	User xyz
+
+Host hpc
+	Hostname coe-hpc1.sjsu.edu
+	User 012404405
+	# I could not get this HPC to install alacritty terminfo to ~/.terminfo by `infocmp | ssh studio 'tic -x /dev/stdin'`.
+	# And the HPC does not have alacritty terminfo in /usr/share/terminfo/a.
+	# And it has issues when me using alacritty as TERM env. And manual copy terminfo to ~/.terminfo does not fix the issues.
+	# Issues are `htop` and `vim` errors.
+	# I still want to use alacritty as TERM env on my laptop, so I choose to set TERM env here. xterm-256color and st-256color both works,
+	# but I want to use alacritty colorscheme. It seems if I set st or xterm as TERM env, alacritty colorscheme is used,
+	# maybe because those TERM env means truecolor?
+	# https://wiki.archlinux.org/title/Alacritty#Terminal_functionality_unavailable_in_remote_shells
+	# https://github.com/alacritty/alacritty/issues/3901
+	SetEnv TERM=st
 
 Host ia
 	Hostname ia.flylightning.xyz
 	User xyz
+
+Host ca
+	Hostname ca.flylightning.xyz
+	User xyz
+
+Host aa
+	Hostname aa.flylightning.xyz
+	User xyz
+
+Host ib
+	Hostname ib.flylightning.xyz
+	User xyz