vps-connectWindows: pick one route
All three routes end at the same place: ssh vps2. Pick the one that fits how you already work — do not mix them up, or your alias will live in a different place than you expect.
| PowerShell (new) | Git Bash | WSL (Ubuntu) | |
|---|---|---|---|
| Script | connect-vps.ps1 | connect-vps.sh | connect-vps.sh |
| You need | Windows OpenSSH client (usually built in) | Git for Windows | WSL + Ubuntu from the Microsoft Store |
| Alias lives in | %USERPROFILE%\.ssh\config — shared with PowerShell and Git Bash | ~/.ssh/config — the same Windows file as PowerShell | Inside WSL only (~/.ssh/config in Linux) |
| After setup, ssh vps2 works in | PowerShell (and Git Bash) | Git Bash (and PowerShell) | WSL terminal only |
| Best for | You live in PowerShell | You already use Git Bash | You want a full Linux terminal |
Recommendation: if you are on Windows and unsure, start with PowerShell — it is the route with nothing extra to install for most Windows 10/11 PCs.
Does NOT work: double-clicking a
.sh file; running ./connect-vps.sh in PowerShell or CMD; running .\connect-vps.ps1 in CMD. A Bash script needs a Bash terminal (Git Bash or WSL), and a PowerShell script needs PowerShell.Quick commands
.\connect-vps.ps1 -Name vps2 -Host <VPS-IP>./connect-vps.sh --name vps2 --host <VPS-IP>ssh vps2See the PowerShell tab for execution-policy help, and the Bash tab for the Bash options.