Fully automate learner setup with Gitpod #260
Merged
Conversation
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
kentcdodds
requested changes
May 5, 2022
.vscode/settings.json
Outdated
| @@ -0,0 +1,5 @@ | |||
| { | |||
There was a problem hiding this comment.
Can we put this in the kcd.settings.json? I don't like surprising people with settings, but they can copy them if they want them.
There was a problem hiding this comment.
Oh yes, I think that's a good call
There was a problem hiding this comment.
Confirmed they have been copied over and the un-suffixed settings.json has been removed
This was referenced May 10, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
After playing around with the Remix blog tutorial in Gitpod, I wanted to see how much the Epic React learner process could be simplified the same way.
Looking at the issues in this repository, most of them are about local dev environment issues, whether they're incompatible Node versions or Windows bugs with the setup scripts. More than half the README.md (all-contributors excluded) is about navigating setup issues too.
After adding the
gitpod.ymlfile, from the time I arrived at the repository, I was able to set up the application in my local VS Code, add my email to the questionnaires, run the tests, and complete the first exercise in under 2 minutes.Everyone who runs this repo in Gitpod can bring their own local VS Code or JetBrains IDE, with all their local settings, but they don't have to worry about having git, node, or npm installed, and the setup scripts will work for windows users too because they're just connecting to a linux environment that does all the work for them.
There is already a CodeSandbox link set up, which solves a similar problem although it only works in the browser and doesn't support the "Set your email" setup script. Gitpod can work in the browser too, but I think it's best to learn new things with the same tools and IDEs you do your regular development in.
You can try this out yourself to see how the workflow feels
I'm not sure if you still intend on running any more Epic React live workshops, but eliminating these sorts of setup difficulties works really well in live workshops and I would love to work through the rest of this course to integrate Epic React