slashrelativepath / relativepath-cycle-5

Source repository for Relative Path Cycle 5
3 stars 0 forks source link

updated README for windows and debian/ubuntu users #19

Closed eld120 closed 10 months ago

eld120 commented 10 months ago

added slightly more descriptive and hopefully accurate instructions for windows and fixed a merge conflict locally + pushed

eld120 commented 10 months ago

Tested the webserver-windows.ps1 script using a windows 11 VM on my slow laptop using a powershell admin shell and setting Set-ExecutionPolicy Bypass - this is notably different from the README (sorry my mistake) but I don't really love the long slow intensive process of building a windows VM on my resource limited laptop.

Thought - we can update the README to reflect the above conditions of the test or run another test with the execution policy set to RemoteSigned.

Note - there were several notices between installation steps saying that I may need to restart powershell in order to use chocolatey but each installation succeeded. I did not have any desire to attempt to launch a multipass ubuntu VM within my Windows VM running on Windows:

image

stephenlauck commented 10 months ago

Tested the webserver-windows.ps1 script using a windows 11 VM on my slow laptop using a powershell admin shell and setting Set-ExecutionPolicy Bypass - this is notably different from the README (sorry my mistake) but I don't really love the long slow intensive process of building a windows VM on my resource limited laptop.

Thought - we can update the README to reflect the above conditions of the test or run another test with the execution policy set to RemoteSigned.

Note - there were several notices between installation steps saying that I may need to restart powershell in order to use chocolatey but each installation succeeded. I did not have any desire to attempt to launch a multipass ubuntu VM within my Windows VM running on Windows:

image

Why are you building a windows VM on your windows machine?

eld120 commented 10 months ago

A VM is a new environment where I can test this script which passed the "works on my machine" test but might not have worked on someone else's machine. I remember you mentioned that the script might not work on someone else's machine but I don't know exactly what else might have gone wrong, so I wanted to test this on a new installation of windows or a VM.