notes for future windows install setup

[dezren39]

hey so i see you have a todo for using choco. this should work fine, i might suggest scoop or winget but any of those would do.

after that though, you'd need to setup docker etc, it might be easier to use wsl 2.0 as a requirement and then have a setup like so

prerequisites:

• docker-desktop (or podman or rancher-desktop)
  • https://github.com/rancher-sandbox/rancher-desktop/releases
• wsl 2.0
• homebrew

and then maybe offer a single path to achieve setup. i use docker desktop but i imagine you'd want to suggest podman or rancher but say that any of them should work. (docker licensing, etc)

• https://docs.brew.sh/Homebrew-on-Linux

  • sudo apt-get install build-essential procps curl file git
    

• https://brew.sh/

  • /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
    

  • 
    • don't forget this step! (per user, represented here $USER)

    • (echo; echo 'eval "$(/home/linuxbrew/.linuxbrew/bin/brew shellenv)"') >> "/home/$USER/.bashrc"
      eval "$(/home/linuxbrew/.linuxbrew/bin/brew shellenv)"
      

  • brew suggests installing gcc?

  • brew install gcc
    

  • brew install typestream
    

new users to docker would benefit more from docker/rancher desktop. (docker will cause businesses especially enterprise heartburn though.)

the simplicity of your windows setup might benefit from podman, though i've had more user issues spawned from local podman setups and rancher has mostly just worked.

some notes:

• podman and rancher will likely install wsl for windows users,
  • wsl sometimes has had issues where i had to go to Microsoft Store and install ubuntu myself, ensure WSL Kernel was updated.
  • https://learn.microsoft.com/en-us/windows/wsl/install-manual
  • https://aka.ms/wslstorepage
  • https://github.com/microsoft/WSL/releases
• if you don't use wsl and you go windows-native, i really recommend adding the following as prerequisite because they will reduce the weird issues people will bring to you:
  • powershell core 7.2 minimum
  • preferably windows 10/11, but it's fine.
  • i would recommend users go to 'Microsoft Store' and install 'Terminal', set their default terminal to powershell core in the terminal settings. but they will probably be fine in a powershell window or from vscode terminal, just have them send you a $PSVersionTable output when debugging so that you know what you're dealing with powershell wise.
  • Windows Key, Search For 'Terminal Settings' or "developer Features' (varies on OS)
    • enable developer mode
    • setup powershell core or terminal as default, enable script execution

[lucapette]

First of all, let me thank you for these notes (and all the other issues you opened!), this is amazing work and I'm grateful.

It's true I have a TODO for choco in the docs, the reason is that I hoped someone would try this out so I'd have the chance to start a conversation around windows support.

The problem is that I have never had a windows machine in my entire life so I have no idea about windows setups for developers, in fact I barely understand your suggestions there.

Of course, I really want to support windows for the "getting started experience" (meaning, I'd exclude any production env... I'm not sure that's even a thing) but it definitely can't do this alone because I don't have the content or the understanding for leading this.

Short term, what I'm thinking is to leave this open and link it from the docs (I will take care of this right after I'm done commenting). The hope being someone will want to take care of this for TypeStream: docs, testing. I could do revamp the docs with your suggestions on my own but I don't feel comfortable with the idea I haven't tested them. Which makes me think: it's unclear to me if you managed to run TypeStream on windows or not?

[dezren39]

Thank you! I did manage to run it through WSL! I intend to try and see what happens from native Windows sometime soon. I agree that Windows installs would typically be non-production/for-development-purposes. If I get more comfortable with all this I might try and help more with the docs.