<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>jekyll on Nullog.net</title><link>https://the.nullog.net/tags/jekyll/</link><description>Recent content in jekyll on Nullog.net</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Mon, 14 Jul 2014 00:00:00 -0400</lastBuildDate><atom:link href="https://the.nullog.net/tags/jekyll/index.xml" rel="self" type="application/rss+xml"/><item><title>Middleman</title><link>https://the.nullog.net/2014/07/middleman/</link><pubDate>Mon, 14 Jul 2014 00:00:00 -0400</pubDate><guid>https://the.nullog.net/2014/07/middleman/</guid><description>I don&amp;rsquo;t want to go dwell to much on the evolution of my online presence. For nearly two years this site has been built upon the awesomeness that is Jekyll. Over the two years I&amp;rsquo;ve learned a lot, I&amp;rsquo;ve also made may mistakes. I do feel in many ways Jekyll with GitHub is nearly a perfect platform for most users. Yet I wanted more and moved the hosting to Heroku. I had the inclination I still wanted more back in November when I started to &amp;lsquo;refactor&amp;rsquo; the site design.</description></item><item><title>5&#43; Hours</title><link>https://the.nullog.net/2013/12/5-hours/</link><pubDate>Fri, 27 Dec 2013 00:00:00 -0500</pubDate><guid>https://the.nullog.net/2013/12/5-hours/</guid><description>I&amp;rsquo;ve been putting of creating a plug-in that would take my images from flickr and embed them on pages here&amp;hellip; was able to make a local working plug in fairly quicky. However, everytime I tried to push the site to heroku everything would fail with an error, Liquid Exception: No API key or secret defined!
Well the solution was simple and I kept glossing over it
heroku labs:enable user-env-compile Yes, thats right.</description></item><item><title>Giving Back</title><link>https://the.nullog.net/2012/09/giving-back/</link><pubDate>Tue, 04 Sep 2012 00:00:00 -0400</pubDate><guid>https://the.nullog.net/2012/09/giving-back/</guid><description>I the course of building and deploying this site one particular site has been truly helpful, Stack Overflow. Today I was finally able to give back and answer a fairly simple question that had me perplex when I first encountered it, Jekyll on Heroku listing additional (internal?) posts I haven&amp;rsquo;t created.
The probelm: Jekyll on heroku publishes mysterious pages, and they all relate to your project someway, somehow.
The solution: Let&amp;rsquo;s call the directory where Jekyll is installed &amp;amp; running from the root /.</description></item><item><title>Create a Post or Page</title><link>https://the.nullog.net/2012/08/create-a-post-or-page/</link><pubDate>Sun, 26 Aug 2012 00:00:00 -0400</pubDate><guid>https://the.nullog.net/2012/08/create-a-post-or-page/</guid><description>Why is it I can never remember:
rake post title=&amp;quot;Hello World&amp;quot; or
rake page name=&amp;quot;about.md&amp;quot;</description></item><item><title>heroku</title><link>https://the.nullog.net/2012/08/heroku/</link><pubDate>Thu, 09 Aug 2012 00:00:00 -0400</pubDate><guid>https://the.nullog.net/2012/08/heroku/</guid><description>After playing with jekyll on Git Hub&amp;rsquo;s pages, I realized I needed something with a bit more zest. I needed plug-in support. I found Jonas Forsberg post entitled Jekyll + Heroku + Unicorn = Blazing fast blogging and basically followed the step outlined below.
sudo gem install heroku sudo gem install bundler heroku auth:login git clone git@github.com:himynameisjonas/jekyll-heroku-unicorn.git cd jekyll-heroku-unicorn bundle install heroku create git push heroku master That lead to a complete fail.</description></item><item><title>prose.io</title><link>https://the.nullog.net/2012/08/prose.io/</link><pubDate>Thu, 09 Aug 2012 00:00:00 -0400</pubDate><guid>https://the.nullog.net/2012/08/prose.io/</guid><description> Prose is a web-based interface for managing text-based content in your GitHub repositories. Use it to create, edit, and delete files, and save your changes directly to GitHub. Prose</description></item></channel></rss>