Porting to Jekyll 3.0 & Octopress 3.0


For those of you who are frequent readers to my site (so very few of you), may notice the new look and feel. The process of porting this over to 3.0 was actually not as bad as i thought it was going to be.

The process mainly consisted of just starting fresh and modifying some of my Travis-CI setup to account for the changes brought on by Octopress 3. Some of my fancy deployment methods needed to be modified a bit to account for the changes brought with 3.0 and how they interact with travis-ci. The biggest change is that now my .travis.yml now cannot integrate posts from stash, as that now has an exit flag of 1 if there are no posts to re-integrate, meaning that travis-ci will think the build has failed.

The new .travis.yml is now as follows:

language: ruby
cache: bundler
rvm:
- 2.2.0
branches:
  only:
  - master
before_install:
- echo -e "Host *\n\tStrictHostKeyChecking no\n" >> ~/.ssh/config
- echo -e "$DEPLOY_PRIVATE_KEY" > ~/.ssh/id_rsa
- chmod 600 ~/.ssh/id_rsa
- eval `ssh-agent -s`
- ssh-add ~/.ssh/id_rsa
script:
    - bundle exec jekyll build #generate static to /public
    - bundle exec octopress deploy #rsync /public to sfo

The act of porting it over also required I tweak my Gemfile a bit, and change which markdown processor I was using from default Jekyll settings. Making sure that I have all of these redcarpet extensions gives me the all the features I want out of a Jekyll blogging platform.

redcarpet:
  extensions: ["smart", "tables", "autolink", "strikethrough", "space_after_headers", "with_toc_data", "fenced_code_blocks", "footnotes"]

The theme is now Pixyll, an absolutely outstanding Jekyll theme by John Otander. It’s so perfect, that I have very little that I need to tweak it with.

Related Posts

Yet Another Octopress2.0 + TravisCI Guide

A Change to Travis

Pubster for Atom

LSI on Travis

Tubster Syntax - Atom

Thoughts on Tay – a Postmortem

pa11y – a Work in Progress Atom Theme

YOURLS Hexadecimal