add mongoDB install clause for wsl2 users. #184
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
not sure if this is the path we would like to take, but raising the question in code if helpful. many 301 students experience a significant time-dump (for students and TAs actually) when trying to install mongoDB locally. The answer always seem to be the same "oh, that thing we told you to do, you don't actually need to do it". Instructions for the "what-if" or "eventuality of" failure would preserve everyone's time and most importantly save student bandwidth for being 301 ready! Can we just call this what it is and reap the quality of life benefits? Alternatively, can the MongoDB install just go away? because we allow WSL usage, using Ajax is just the way we teach them anyway! why have half the class install mongoDB which is never used locally anyway!
kassiebradshaw
approved these changes
Jan 5, 2023
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.
not sure if this is the path we would like to take, but raising the question in code if helpful. many 301 students experience a significant time-dump (time dump for students and TAs actually) when trying to install mongoDB locally. The answer always seems to be the same "oh, that thing we told you to do, you don't actually need to do it".
Instructions for the "what-if" or "eventuality of" failure would preserve everyone's time and most importantly save student bandwidth for being 301 ready! Can we just call it out and reap the quality of life benefits across the org?
Alternatively, can the MongoDB install just go away, even if just for now? because we allow WSL usage, using Ajax is just the way we teach them in class anyway! why have half the class install mongoDB which is never used locally?