- collaboratively outline TheBest™ Windows setup and best-practices in order to
- create an “official” Redwood Doc for enhancing the experience of people developing Redwood on Windows?
This post is a Wiki. Anyone with Forum Trust Level 1 permissions is able to contribute.
How to Participate
Please edit, add, comment, and, most of all, improve the content below! Once it feels like we’ve reached a kind of consensus, we can migrate this Post to an official Redwood Doc.
—Edit Everything Below—
Developing Redwood on Windows
[What is working. How developer experience should “feel”. Startup and installation times. Etc. Need to define the overall vision for Redwood experience on Windows, which, importantly, will set constraints as much as it sets benchmarks + expectations.]
Note: I suggest we focus this specifically on “Developing Redwood Projects on Windows” and not “Developing the Redwood Framework on Windows”. For the latter, I believe we have good-enough instructions within the Contributing docs. Will defer to Tobbe.
[Windows, Node, Yarn, etc]
[Which one(s)? Does Windows Terminal belong here?]
Storage: Physical (and maybe Remote)
[A bunch of things I (David) don’t understand: Local HDD, Local SSD, Local nVME, Remote NAS, Remote SAN, Over SSH (e.g. VSCode’s Remote SSH), Over CIFS/SMB (e.g. A “Windows share”), Over NFS… oh my]