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

Can't build jekyll docs on macOS Mojave #1437

Closed
benjamingeer opened this issue Sep 11, 2019 · 3 comments · Fixed by #1459
Closed

Can't build jekyll docs on macOS Mojave #1437

benjamingeer opened this issue Sep 11, 2019 · 3 comments · Fixed by #1459
Assignees

Comments

@benjamingeer
Copy link

I installed Jekyll following the instructions here:

https://jekyllrb.com/docs/installation/macos/

I had to install Ruby using Homebrew as described there, because Mojave's built-in Ruby is too old for Jekyll.

docs/makeSite then complained about many gems it couldn't find. I installed each of these manually.

Now if I use the existing Gemfile.lock, it complains:

[error] /usr/local/lib/ruby/site_ruby/2.6.0/bundler/runtime.rb:319:in `check_for_activated_spec!':
You have already activated public_suffix 4.0.1, but your Gemfile requires public_suffix 3.0.3.

If I rm Gemfile.lock and regenerate it using bundle install, docs/makeSite complains:

[error] /Users/benjamingeer/.gem/ruby/2.6.0/gems/bundler-2.0.2/lib/bundler/runtime.rb:319:in `check_for_activated_spec!':
You have already activated i18n 1.6.0, but your Gemfile requires i18n 0.9.5.
@subotic
Copy link
Collaborator

subotic commented Sep 11, 2019

yes, compiling the docs locally with jekyll is always making problems. That is why, for https://github.com/dasch-swiss/dsp-docs we are using MkDocs.

@benjamingeer
Copy link
Author

benjamingeer commented Sep 11, 2019

MkDocs looks like it’s the same thing as Jekyll, except that it’s written in Python instead of Ruby... Is the idea that Python handles library dependencies better than Ruby?

@subotic
Copy link
Collaborator

subotic commented Sep 11, 2019

Yes, managing python dependencies is much easier (for me at least). Also, we use Python in other contexts. Messing with the whole Ruby installation just for docs generation is a bit of an overkill.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants