-
Notifications
You must be signed in to change notification settings - Fork 631
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Local-build-instructions #2922
Local-build-instructions #2922
Conversation
✅ Deploy Preview for the-turing-way ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
spotted a few places where new sentences weren't on a new line
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this @arronlacey! I have a few suggestions to clean up the language, and I think the second section needs to be more narrative style rather than bullet points.
|
||
## Step-by-step guide | ||
1. Install miniconda https://conda.io/projects/conda/en/latest/user-guide/install/index.html#regular-installation | ||
2. Run `conda init` in your terminal. You should see `(base)` in your prompt indicating that conda was successfully installed and you are now in it's base environment. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We maybe want to be explicit about "open your terminal app and run the conda init
command"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, i agree with this.
And to add to it, my cmd did not recognize the conda init
, i had to use the Anaconda prompt(miniconda3) terminal to run it. I will suggest adding a clue to that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Anaconda and miniconda are different installations. Are you sure you installed miniconda, as per the instructions? Did your machine already have anaconda installed before you started?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, i followed the instruction for installation https://conda.io/projects/conda/en/latest/user-guide/install/index.html#regular-installation, I selected for windows.
No i never had the Anaconda on my machine.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Huh, ok. This is probably a "things are different on Windows" scenario, so we should have a nested bullet point here saying "on windows, do this instead"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi both - hopefully I've addressed the comments in this conversation in commit c3c7dda . Namely adding more narrative and the point about needing Anaconda prompt on Windows
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you sure you pushed the narrative changes? I'm examining commit c3c7dda
(#2922) but it looks pretty similar to me? I'm imagining that we get rid of the bullet points under "Why did we recommend using (mini)conda?"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah I was looking at the wrong section - I added some very light touch edits on the build instructions in c3c7dda. Ok no problem I'll have a crack at the miniconda section.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2ca45fa is hopefully more what you had in mind, and the title is now in line with the toc
@sandygudie and @RealRichi3 - maybe this would be of interest for you all? We'd love to see if there instructions make sense for you all to build the book currently on your local machines. (Tagging @BatoolMM for awareness). |
Alright @aleesteele, we'll look into it and make the necessary changes, thanks |
@aleesteele i went through the guide and it looks really good, although i have an issue. Under the section |
Another question @aleesteele, should we go ahead and add the changes suggested by @sgibson91 ? |
Yes, the step |
Oh, i understand better now, thanks @sgibson91 |
@aleesteele, the guide is okay, i was able to setup the project build locally |
The instructions work for me as well and were super helpful :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Welldone @arronlacey
I was able to build the Jupterbook successfully, I also dropped a couple of comments.
Co-authored-by: Sarah Gibson <44771837+sgibson91@users.noreply.github.com>
Co-authored-by: Sarah Gibson <44771837+sgibson91@users.noreply.github.com>
Co-authored-by: Sarah Gibson <44771837+sgibson91@users.noreply.github.com>
Co-authored-by: Sarah Gibson <44771837+sgibson91@users.noreply.github.com>
Co-authored-by: Sarah Gibson <44771837+sgibson91@users.noreply.github.com>
Co-authored-by: Sarah Gibson <44771837+sgibson91@users.noreply.github.com>
Co-authored-by: Sarah Gibson <44771837+sgibson91@users.noreply.github.com>
Co-authored-by: Sarah Gibson <44771837+sgibson91@users.noreply.github.com>
Co-authored-by: Sarah Gibson <44771837+sgibson91@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well done @arronlacey @RealRichi3 @samkitk @RealRichi3! 🚀
Co-authored-by: Goodnews Sandy <54219127+sandygudie@users.noreply.github.com>
Co-authored-by: Goodnews Sandy <54219127+sandygudie@users.noreply.github.com>
Co-authored-by: Sarah Gibson <44771837+sgibson91@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great to me now. Thank you @arronlacey!
Co-authored-by: Sarah Gibson <44771837+sgibson91@users.noreply.github.com>
Co-authored-by: Sarah Gibson <44771837+sgibson91@users.noreply.github.com>
Thank you @sgibson91, @sandygudie, @RealRichi3 @aleesteele @samkitk for working together on this. |
Summary
Adds some documentation to build the Turing Way Book locally. Original instructions proposed via the Infrastructure group and written by @sgibson91, edited by @arronlacey
List of changes proposed in this PR (pull-request)
jupyter-book
What should a reviewer concentrate their feedback on?
Acknowledging contributors