Trying Ruby Rails Again

A while back, I tried installing and using Ruby and/on Rails. I think it was so I could use Jekyll so I could contribute to an open source project. If memory serves, it was a nightmare.

Once again, I want to try Jekyll but, this time, so I can blog my VPS stuff on my gitHubPage ( so that effort goes toward my building of a greens-squared kingdom that probably looks like a giant, green Minecraft castle.

I created my gitHubPage following their official Roll Vanilla tute-guide. It ends with a link to Blogging with Jekyll which I still wanted to play with so I followed–not that link, but–the Learn how to set up Jekyll link to Jekyll’s own Quick-start guide which begins with the ominous and vague

“If you already have f full Ruby development environment with all headers and RubyGems installed…”

So I had to do that.

First, I uninstalled RVM because the Internet told me to. Yes, there were reasons that I read in blog posts that seemed good to me but, basically, that means the Internet told me to use rbenv instead.

I by basically following Setup Ruby On Rails on Ubuntu 14.04 Trusty Tahr.

I skipped installing the dependencies because I already installed Ruby a while back.

ruby --version showed me I had v2.3.0p0

I copied and pasted the first two “paragraphs” of code from Using rbenv and got yelled at by my terminal so then I actually installed rbenv first, as instructed, via

sudo apt-get install rbenv

The latest version of Ruby is the tiniest bit newer than the instructions so I then typed in

rbenv install 2.4.1

and here we sit … waiting …

… geez …

Okay, now rbenv global 2.4.1 and ruby -v gives me Ruby v2.4.1p111

I skipped the rest of that tute because I already have MySQL, Node, and have no need (yet) for PostgreSQL.

I updated my Gems v2.5.2 (probably from the last time I tried all this) via

gem update --system

and now have a shiny new RubyGems v2.6.12

I don’t think I need Rails for anything at the moment but since I’ve never heard of one without the other, I

gem install rails

I notice that during this, it installs nokogiri (and 37 other gems) for me which is cool because some tute said I should do that anyway because it’s a dependency for tons of stuff. “Building native extensions. This could take a while,” Terminal said. And it did.

Then I started the Jekyll Quick-Start Guide (QSG) mentioned above beginning with

gem install Jekyll bundler

20 more gems installed. It scares me how smoothly all this is going. I’m sure my laptop will explode any second now. Even though I plan to build my for real Jekyll site in my GitHubPage local repo, I’m new at this, so I continued with the QSG tute. Nope, you know what? I’m just gonna throw caution to the wind.

Navigated into the aforementioned local repo and

Jekyll new . --force

Jekyll new . installs the site in the directory I’m in and --force makes it do that even though this directory isn’t empty (there’s a readme.MD file and the index.htm file I created following Roll Vanilla.

To take a gander at my new monster, I

bundle exec Jekyll serve

and visited http://localhost:4000 and saw … what looks like the index page I made. Wha?

Ooh, wait! Looking in the folder, I see there’s also a file and I’ll bet that’s supposed to be the home page so after deleting my htm file and refreshing … BEHOLD!


I see some SASS in the folder so I finally have a practical way to play with and learn that. Kewl. Now I have to learn to make posts and upload/push this stuff and figure out how that works now … it never ends.