Skip to content
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

Webricks currently not included by default in homebrew's ruby, leading to issues. #20562

Closed
1 task done
AlDacMac opened this issue Sep 12, 2022 · 6 comments · Fixed by #21557
Closed
1 task done

Webricks currently not included by default in homebrew's ruby, leading to issues. #20562

AlDacMac opened this issue Sep 12, 2022 · 6 comments · Fixed by #21557
Labels
content This issue or pull request belongs to the Docs Content team good first issue Good for newcomers help wanted Anyone is welcome to open a pull request to fix this issue pages Content related to GitHub Pages

Comments

@AlDacMac
Copy link

AlDacMac commented Sep 12, 2022

Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll

What part(s) of the article would you like to see updated?

When following this article with ruby installed via homebrew, I I encountered the following error when trying to locally test my site: /Users/<user>/.gem/ruby/3.1.2/gems/jekyll-3.9.2/lib/jekyll/commands/serve/servlet.rb:3:in require': cannot load such file -- webrick (LoadError)`.

As discussed on this stackoverflow article, the issue is that webrick is not being included when homebrew is used to install Ruby 3.1.2: https://stackoverflow.com/questions/69890412/bundler-failed-to-load-command-jekyll.

I would suggest adding a line mentioning this, and telling the user to run bundle add webrick if they have used homebrew to install an affected version of ruby. Alternately, this specific error could be added to the troubleshooting jekyll errors section.

Additional information

No response


[maintainer edit]

Content plan here

@AlDacMac AlDacMac added the content This issue or pull request belongs to the Docs Content team label Sep 12, 2022
@welcome
Copy link

welcome bot commented Sep 12, 2022

Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Sep 12, 2022
@hegdepavankumar
Copy link

yeah good idea.

@cmwilson21
Copy link
Contributor

@AlDacMac Thanks so much for opening an issue! I'll triage this for the team to take a look 👀

@cmwilson21 cmwilson21 added waiting for review Issue/PR is waiting for a writer's review pages Content related to GitHub Pages and removed triage Do not begin working on this issue until triaged by the team labels Sep 13, 2022
@isaacmbrown
Copy link
Contributor

isaacmbrown commented Oct 18, 2022

Hi @AlDacMac, thanks for opening this issue! ✨ This is clearly a problem that a lot of people have run into (e.g. github/pages-gem#752).

You or anyone else is welcome to open a PR to fix this. I'll include a very simple content plan below so it's easy for someone to identify the change.

Content plan

Running bundle exec jekyll serve to run your GitHub Page site locally can lead to an error if you're using a >3.0 version of Ruby, which doesn't come with webrick installed.

Audiences

Developers testing their Pages sites locally.

Documentation plan

In "Testing your GitHub Pages site locally with Jekyll," under the "Building your site locally" subsection, add a note under the codeblock in step 4 ({% note %} **Note:** ... {% endnote %}). Mention that:

  • If you've installed Ruby 3.0 or later (which you may have if you installed the default version via homebrew), you might get an error at this step. That's because these versions of Ruby no longer come with webrick installed.
  • To fix the error, try running bundle add webrick, then re-running bundle exec jekyll serve.

@cmwilson21 cmwilson21 added help wanted Anyone is welcome to open a pull request to fix this issue and removed help wanted Anyone is welcome to open a pull request to fix this issue labels Oct 18, 2022
@dojutsu-user
Copy link
Contributor

Hi @cmwilson21,
Taking this issue up.

@Rambo250000000000

This comment was marked as spam.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content This issue or pull request belongs to the Docs Content team good first issue Good for newcomers help wanted Anyone is welcome to open a pull request to fix this issue pages Content related to GitHub Pages
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants