Can I somehow just make netlify build use zsh, or does it need to use bash?
Some stuff I already tried:
Adding the following to my otherwise empty .bash_profile:
export PATH="/usr/local/opt/ruby/bin:$PATH"
if which ruby >/dev/null && which gem >/dev/null; then
PATH="$(ruby -r rubygems -e 'puts Gem.user_dir')/bin:$PATH"
fi
Nice! This sounds like a fun one first, which version of macOS are you using? The default system shell switched to Zsh in… I think Catalina, so if you’re already on Catalina, the following may be moot…
While it may be some shell churn or something like that; try running bundle exec jekyll build and see if that resolves?
Thanks, but I already gave that a try. I figured there might be a way to make Netlify Build rely on zsh, which is why I posted here.
It’s unfortunately also not working… And yes, I’m on Catalina, but had been using zsh for a few years prior to that. Did a fresh install of Catalina when upgrading, though.
Thanks for your help guys I’ll see if I can find help on SO or somewhere else. Or maybe I’ll just skip using Netlify Build for the time being.
Hm. I mean I too have been running Zsh for years and run all of my local netlify dev just fine with it, but I wonder if your PATH is augmented only by Zsh and Bash isn’t getting those same augmentations let us know if you find something that works!
I am having a similar issue for which the cause appears to be the same on MacOS Catalina. I am using gulp/jekyll and the latest version of ruby installed using brew. This set up allows me to run gulp / jekyll commands without sudo. Catalina comes with an older version of ruby pre-installed and brew installs a newer version in a different path, which is set in .zshrc so that the ruby/gems commands are executed using the newer version.
When I attempt to run netlify build command, it somehow is picking up the older Catalina version and thus cannot find some gems plugins that were installed in the newer version of ruby. It appears that the command is somehow not inheriting the paths of the user which runs the command.
It would be helpful to know how others have worked around this and whether or not there is a way to set paths for netlify-cli or tell it which version of ruby to use. I have tried to override Ruby version using the steps in this doc, however that seems to have no effect when running netlify build command locally.
Hi @duveedigital, the doc you mentioned are ways to set versions for the buildbot when building on Netlify, not locally. That’s likely why it’s not working for you.
Have you tried running echo $PATH to see if the new Ruby version is in your path? If not, could you try prefixing export PATH=$PATH:<path/to/ruby> to the netlify cli command?
Hi @duveedigital and @tkrunning. What you are experiencing is a common issue unfortunately due to incomplete documentation on the Jekyll site. The solution is to update your PATH with the location where gems get installed when you are using the Homebrew version of Ruby. If you’re using Ruby version 2.7.x, that location is /usr/local/lib/ruby/gems/2.7.0/bin. If your current Ruby version is something other than 2.7.x, then replace 2.7 with the first two digits of your Ruby version, then run this command:
Replace .zshrc with .bash_profile if you’re using bash instead of zsh.
Helping people set up a proper Ruby development environment on their Mac is a passion of mine. I’ve been doing it for the past 9 years. It saddens me that people have to go through the same issues over and over. I wrote a script that can automate the whole process, and I wish that practice was more widespread. Why make people do things manually when it is almost guaranteed to result in errors due to missing steps or human error?
first, which version of macOS are you using? The default system shell switched to Zsh in… I think Catalina, so if you’re already on Catalina, the following may be moot…
I’ll see if I can find help on SO or somewhere else. Or maybe I’ll just skip using Netlify Build for the time being.
let us know if you find something that works!