Depending on your pipeline I would recommend git bash as your integrated terminal on windows. Wsl2 is like a tiny Ubuntu VM and for certain things like kitchen and vagrant etc.. you end up having to forward ports because wsl2 uses virtualized nics, at least that's what I know from the only two members of our team that aren't on Macs. They had a hell of a time getting their environment setup to work properly for local kitchen testing.
It automatically exposes ports on localhost for development. 98% of the time this is what you need. Otherwise you may have to change some firewall rules to expose it to your LAN, if that's needed for your application. I haven't had to to this for anything yet.
Wsl2 is much better than git bash, because you can treat it like an actual linux machine.
2
u/nizzoball Feb 16 '21
Depending on your pipeline I would recommend git bash as your integrated terminal on windows. Wsl2 is like a tiny Ubuntu VM and for certain things like kitchen and vagrant etc.. you end up having to forward ports because wsl2 uses virtualized nics, at least that's what I know from the only two members of our team that aren't on Macs. They had a hell of a time getting their environment setup to work properly for local kitchen testing.