Add Windows WSL installation guide for Foundry#156
Open
Grandoloye2107 wants to merge 1 commit intotempoxyz:mainfrom
Open
Add Windows WSL installation guide for Foundry#156Grandoloye2107 wants to merge 1 commit intotempoxyz:mainfrom
Grandoloye2107 wants to merge 1 commit intotempoxyz:mainfrom
Conversation
|
@Grandoloye2107 is attempting to deploy a commit to the brendan-7108's projects Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The current Foundry installation guide only shows the curl command which fails on Windows with a certificate error. There's no mention of WSL being required. Tested this today on Windows 11, the command silently fails and foundryup is not recognized. Added a Windows tip box explaining WSL is required, how to install it, and a note that the verification pending warning during deployment is normal and not an error. Both issues are undocumented and will trip up any Windows user trying to deploy on Tempo for the first time.