Support for bundler

[subosito]

Instead of letting people manage different version of jekyll and other gems. I think it's better to utilize bundler's Gemfile. Then we can always same version of gems, and use same way of execute jekyll via bundle exec jekyll. What do you think?

Note: This Gemfile contains Jekyll 1.0.

[plusjade]

Agreed. I think it's most important to always default to the official GitHub Pages version though in order to keep with the "100% compatible with GitHub Pages" philosophy. With that said, JB should only be converted to jekyll 1.0 when GitHub Pages officially supports jekyll 1.0 . We can easily track a jekyll-1.0 branch though to have it ready when the time comes!

[subosito]

Fortunately, Github Pages officially support jekyll 1.0, see https://help.github.com/articles/using-jekyll-with-pages. I've just upgrade my blog to jekyll 1.0 and it works well (I mean there are no changes at all, at least on my blog).

[plusjade]

Oh cool. When I read the initial post on HN, it was stil in the works. Looks like its done now!

[subosito]

I've tested JB with Jekyll 1.0, here's the result:

$ bundle exec jekyll -v
jekyll 1.0.0

$ bundle exec jekyll build
Configuration file: /mnt/code/github/jekyll-bootstrap/_config.yml
       Deprecation: Auto-regeneration can no longer be set from your configuration file(s). Use the --watch/-w command-line option instead.
            Source: /mnt/code/github/jekyll-bootstrap
       Destination: /mnt/code/github/jekyll-bootstrap/_site
      Generating... done.

Related issue #155, I think the issue is on liquid, because the error is Liquid Exception: undefined method 'sub' for nil:NilClass in 2013-01-31-entityforname-could-not-locate-an-nsmanagedobjectmodel-for-entity-name.md.