-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
Error when attempting to serve: bundle exec jekyll s
#245
Comments
Hi @mattpopovich,
All dependencies are listed on Gemfile.lock
Not yet. My local machine runs on According to the log you provided, I found issue #8523 in the Jekyll repo, and this answer should be useful to you. If not, please inform me. Thank you for reporting this issue. |
@cotes2020 speedy and fantastic answer, as always! For any of those that run into the same issue, I ran |
@cotes2020 added PR #247 that implements this fix. |
…#344) Since version 3.0, Ruby has no `webrick` that Jekyll (<= 4.2) needs
Checklist
master
branch.Describe the bug
I'm updating my webpage from ~September 2020 to ~January 2021. I see that the old build and run scripts have been replaced in favor of
jekyll s
andjekyll b
. When I first attempted to run them I got an error:I then followed the steps on the Jekyll Docs to make sure everything was updated.
Building works without error. The following issue occurs when I attempt to serve:
To Reproduce
Steps to reproduce the behavior:
Follow the tutorial on macOS Catalina, install all newest versions of Jekyll, attempt to serve master branch.
Expected behavior
localhost:4000 would show / render the chirpy site
Screenshots
N/A
Software
Desktop
Smartphone
N/A
Additional context
What versions of dependencies are you running? Is it possible that my ruby version is too new? I've listed my installed versions above. Have you tested this with ruby 3.0?
I also attempted to update brew and got this message that I don't ever remember seeing before when updating brew:
Which, after fetching, I was able to update brew successfully. Not sure if that would have anything to do with it.
Thanks again for all your work maintaining this repository!
The text was updated successfully, but these errors were encountered: