-
Notifications
You must be signed in to change notification settings - Fork 227
Additional step suggested for Mac users of "Building Static Sites with Jekyll" #1669
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
Comments
Thanks, @spswanz! I'll take a look at it. |
@mariechristineb is going to test this for us as part of a 'bug testing' trial #1817 . She will make a recommendation to @svmelton about how we should proceed. |
fwiw, I'm not sure this is long term fix with Mac switching from bash to zsh in Catalina OS, but I'm afraid I don't have more insight. |
Will have to keep an eye on this together with @JoshuaGOB because we have a group of DHers in Argentina translating that lesson. |
@jenniferisasi in general it would be helpful for translating teams to inform us when lessons with bugs are being translated. That's an efficient way for us to address these problems. How can we make sure that information gets where it's needed? |
We were informed about the translation of this particular lesson long ago (Jan 21 for March 30 but then covid19 happened); so the translation proposal arrived earlier than the bug notification... that to say we need to have a system to inform both ways (bug reported before translation started & translation in process while bug is reported). The teams have their project tracking system, could we use them to report also about bugs and cross-reference them? |
I think that is good idea @jenniferisasi |
In the installing Ruby Gems and Jekyll phase, my Mac users have received an error that they don't have write permissions to the ruby gems directory.
This is the suggested fix in the instructions:
That did not working for us, but the following did:
Typing this command:
echo 'export PATH="/usr/local/opt/ruby/bin:$PATH"' >> ~/.bash_profile
Then this command:
source ~/.bash_profile
That fix derived from here:https://stackoverflow.com/questions/51126403/you-dont-have-write-permissions-for-the-library-ruby-gems-2-3-0-directory-ma
The text was updated successfully, but these errors were encountered: