3 ms·
I use a similar set up and wrote about it a while ago too. One thing you may want to consider doing is mount your drives in WSL so that Docker volumes work. Wi
by nickjj 9y ago
I use a similar set up and wrote about it a while ago too.
One thing you may want to consider doing is mount your drives in WSL so that Docker volumes work. With your current set up, none of your volumes would work.
Details on how to do that can be found on:
https://nickjanetakis.com/blog/setting-up-docker-for-windows-and-wsl-to-work-flawlessly#ensure-volume-mounts-work https://nickjanetakis.com/blog/setting-up-docker-for-windows...
Also, in case anyone is wondering "why not just use a VM"? I did for ~5 years but the WSL set up is a lot nicer for day to day development.
Detailed on the VM set up vs WSL can be found on:
https://nickjanetakis.com/blog/using-wsl-and-mobaxterm-to-create-a-linux-dev-environment-on-windows https://nickjanetakis.com/blog/using-wsl-and-mobaxterm-to-cr...
With the above WSL set up, the development performance is pretty nice I must say. Around 250kb of SCSS runs through a fully Dockerized webpack chain (sass-loader, precss, autoprefixer, css-loader) in 1.8 seconds and live reload works. I haven't even began to try and optimize it with fast-sass-loader and other tweaks. I'm also using the stock node-sass package.
15k+ line Rails apps with 75+ gems also reload in under 100ms for code changes (non-assets).