Jan 8, 2013
Once upon a time, I really enjoyed writing in my blog. I documented lots of little bits and pieces of my life. Hey check out how to automate Word document creation with headless Open Office. Hey look at this beautiful roast chicken and root vegetables I just made. Hey read my rant about Python vs PHP. While I enjoyed blogging, the website/server maintenance part of it sucked because I had to keep Wordpress updated and run
yum update semi-religiously to ensure that my server didn’t get taken over by a bunch of script kiddies, all to protect a few dozen blog entries.
The sensible thing would have been to move my blog over to Wordpress.com or Blogspot or something, but instead I ended up shutting my doors. School was stressful, my job was demanding, and I was more than likely trying to impress a girl. I wanted to continue writing about software and software development, but the barrier for continuation was just too damn high.
A couple years ago, I was reading through the blog of Tom Preston-Werner, co-founder of Github. In a post titled blogging like a hacker, Tom wrote about the annoyance of complicated blogging engines and being “stuck in a cycle of quitting and starting over” when he created Jekyll. Dude, I totally feel you. I realized that having my site be just a bunch of static HTML meant:
Even though I didn’t set out to do anything about it right away, I made a mental note to go back to it some day.
Come New Year’s Eve 2012, I decided that my one single resolution would be to pick up writing again. But how to proceed? Ah, there’s that crusty old mental note I accidentally washed with my jeans. I didn’t want to enter a cycle of spending forever on the selection and setup process again though. That thing that sabotaged me time and again. This time, I’d do it in…24 hours or less.
In the true fashion of not hurriedly picking the first tool I encountered, I spent some time playing with Hyde and with Middleman. At the end of the day (hour) however, Jekyll was the winner for me. YMMV. If you want to take the quickest route possible, just fork the source for Tom’s site and push it to your own Github repo. Bam, the magic of Github Pages. If your situation is special, articles about how to set up Jekyll are all over the place. In either case, here’s a really quick guide to how I set up this site.
Pre-requisites: You need Git and Ruby, so if you’re on a Mac, just go ahead and follow this tutorial and get those taken care of. All done? Okay, now let’s move onto the actual Jekyll setup. I should start off by saying that my development environment at home is Mac OS X (10.8) and I spend the majority of my day otherwise at a Linux console. I’m not really going to list out each console command here, since if you’ve decided to go down the Jekyll route, you better be comfortable with Googling for answers.
git initinside of an empty folder. This is pretty much how I start every project.
Source available at needcaffeine/vicvijayakumar.com.
My under 24 hours MVP meant that I wasn’t going to bother with something to help me auto-deploy to Amazon S3, especially because I already use the very powerful and amazing s3cmd to do my backups et al. When I need to push my site up to S3, all I do is
s3cmd sync --acl-public _site/* s3://vicvijayakumar.com/.
So that’s where we are. You are currently reading this on a site produced with the help of Jekyll in under 24 hours. While only time will tell whether I find the whole process awesome enough to continue writing, all signs point to a strong yes at present. Let’s revisit this post in 6 months.