$ cd ~/.rbenv & src/configure & make -C src I've had a few bad experiences with Homebrew, so I decided to install it manually: $ git clone ~/.rbenv The next step was to, following the advice on this SO page, install a Ruby version manager. And while the troubleshooting pages recommend running commands such as sudo gem update -system, sudo gem install jekyll, and sudo gem install -n /usr/local/bin jekyll I didn't want to mess around with the system version of Ruby, and knew that I shouldn't need to use sudo for this, if I set it up right. I try to use /usr/local/bin for the binaries I install anyway, so this made sense: $ gem install -n /usr/local/bin jekyll The first workaround I tried was changing the location where the gem would be installed.
With a little Googling and reading on the Jekyll Troubleshooting page, it turns out this is because, unsurprisingly, the system defaults to using the version of Ruby installed by Apple. You don't have write permissions for the /Library/Ruby/Gems/2.0.0 directory They said the best way to install it was using RubyGems, which I hadn't used before, but seemed easy enough, so I ran the command: $ gem install jekyllĪnd promptly got the response: ERROR: While executing gem. I started out well enough, using the Jekyll Installation Docs. In hindsight, it seems that I made things significantly more difficult by starting with TinyPress, instead of just RTFM for Jekyll and Github Pages myself. As such, it contains a lot of dead ends before I got it all working. What follows isn't a guide it's just my log of the 600+ mistakes it took for me to get started using Jekyll.
As I went to write it I noticed that 's SSL certificate had expired, so it seemed as good a time as any to dive into Jekyll and handle this static blogging with Github Pages myself. This was supposed to be a post complaining about the standards, or lack thereof, applied by ThemeForest, to the Wordpress Themes they well.
0 kommentar(er)
