-
-
Notifications
You must be signed in to change notification settings - Fork 9.9k
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
Update windows.md #5683
Update windows.md #5683
Conversation
Added an update to installation instructions, as a cert authority change in Ruby causes problems with the prior recommended version of Ruby.
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.
Requesting some changes..
@@ -20,6 +20,9 @@ For a more conventional way of installing Jekyll you can follow this [complete g | |||
|
|||
[windows-installjekyll3]: https://labs.sverrirs.com/jekyll/ | |||
|
|||
\[Update 12/23/2016\]: Updates in the infrastructure of Ruby may cause SLL errors when attemptying to use gem install on a version of ruby older than 2.6. (The ruby package installed via the Chocolatey tool is version 2.3) If you have installed an older version, you can update ruby using the directions [here.][ssl-certificate-update] |
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.
Suggesting a couple of edits :
- I don't think including a date is necessary. The information is not fresh-off-the-press and it is understandable by only mentioning the version-number.
- its SSL instead of SLL;
- gem install should be within backticks.:
gem install
- its not "...ruby older than 2.6" but "...RubyGems Package older than 2.6."
- again, "The RubyGems package installed via the Chocolatey.."
- ...update RubyGems package using the directions [here]..."
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.
Thank you for the review, appreciate the feedback!
revising terminology to avoid ambiguity and moving in relation to alternative install instructions.
fixing typo
@@ -16,7 +16,7 @@ A quick way to install Jekyll is to follow the [installation instructions by Dav | |||
2. Install Ruby via Chocolatey: `choco install ruby -y` | |||
3. Reopen a command prompt and install Jekyll: `gem install jekyll` | |||
|
|||
Updates in the infrastructure of Ruby may cause SLL errors when attempting to use `gem install` on a version of the RubyGems package older than 2.6. (The RubyGems package installed via the Chocolatey tool is version 2.3) If you have installed an older version, you can update the RubyGems package using the directions [here.][ssl-certificate-update] | |||
Updates in the infrastructure of Ruby may cause SSL errors when attempting to use `gem install` on a version of the RubyGems package older than 2.6. (The RubyGems package installed via the Chocolatey tool is version 2.3) If you have installed an older version, you can update the RubyGems package using the directions [here.][ssl-certificate-update] |
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.
How does the following sound? I think its better.. 😉
- when attempting to use `gem install` on a version of the RubyGems package older than 2.6.
+ when attempting to use `gem install` with versions of the RubyGems package older than 2.6.
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.
agreed, it flows better.
/cc @jekyll/documentation |
What's the appropriate action to take here? Should I be leaving this thread open until someone with write access decides whether to merge it? |
@jekyllbot: merge +docs |
Thanks! |
Added an update to installation instructions, as a cert authority change in Ruby causes problems with the prior recommended version of Ruby.