Windows 10 Development
While I still am used to my preference of debian based host operating systems for development workflows (gh repo clone icanccleary/ubuntu-dev-playbook), this is a some documentation around what I've installed and what my development workflow on Windows 10 is like.
Edit: This allows me to build a docker contianer, use git, make, npm, and ssh keys on Windows. However, if I want to do anything with network mounts or anything more serious, I avoid Windows. Please treat this as some notes on how to install some software tools on Windows and a few helpful tips along my adventure.
Chocolately to install Node
After you have it installed, proceed to https://community.chocolatey.org/packages/nodejs-lts
Docker for Windows
Adding SSH Keys to Windows
Make sure you're running as an Administrator!
# By default the ssh-agent service is disabled. Allow it to be manually started for the next step to work. # Make sure you're running as an Administrator. Get-Service ssh-agent | Set-Service -StartupType Manual # Start the service Start-Service ssh-agent # This should return a status of Running Get-Service ssh-agent # Now load your key files into ssh-agent ssh-add ~\.ssh\id_ed25519
Edit to load automatically:
It's best to configure OpenSSH Authentication Agent service to automatically start. Alternatively, you can start it manually every time when opening powershell for the first time:
To have SSH agent to automatically start with Windows, you can run (from elevated powershell prompt):
Set-Service ssh-agent -StartupType Automatic
After that, you need to add your ssh key once:
Now everytime the ssh-agent is started, the key will be there. You can check which keys are registered with the ssh-agent:
Above doesn't seem to work.
Git Bash terminal does.
https://github.com/microsoft/terminal/issues/7200#issuecomment-672786518 gets rid of screen white flicker
Select Git Bash inside VS Code
Make install with choco
Open Powershell as administrator
choco install make
Experience So Far
I'm going to stick with a Hyper-V Virtual Machine if I need to do anything serious on a Windows host. My preference is to encapsulate what I know works wihtin a fast enought VM on a Windows Host. My current employer is very tied into Windows and this is just a better experience for me.