tigefa 1.1.2 → 1.1.3

checksums.yaml

@@ -1,7 +0,0 @@
----
-SHA1:
-  metadata.gz: f57331b1db378c3cc4e6ba0e683cbce9bd95f1bd
-  data.tar.gz: b2f4a0d9c6792ff0d489c7968da1fb07ff1a5d51
-SHA512:
-  metadata.gz: c9d05edf9e30a706f2d6e47c19b6d5c5297c04634a4203d10ba7149796ff26e268b4d083ad6f18ec9ec7b504eca429a5ece24e0e524f8dd80e4e8a9aae89054a
-  data.tar.gz: 86ab6f8e9f503c7183f746224d26d13c72eafed7573dac0634546f702afd4f619e19310d81e950c7c0030037c76e076e6a26cb1cfbcb1a77ae2384d52d3f0502

data/features/data.feature

@@ -1,65 +0,0 @@
-Feature: Data
-  In order to use well-formatted data in my blog
-  As a blog's user
-  I want to use _data directory in my site
-
-  Scenario: autoload *.yaml files in _data directory
-    Given I have a _data directory
-    And I have a "_data/products.yaml" file with content:
-      """
-      - name: sugar
-        price: 5.3
-      - name: salt
-        price: 2.5
-      """
-    And I have an "index.html" page that contains "{% for product in site.data.products %}{{product.name}}{% endfor %}"
-    When I run jekyll
-    Then the "_site/index.html" file should exist
-    And I should see "sugar" in "_site/index.html"
-    And I should see "salt" in "_site/index.html"
-
-  Scenario: autoload *.yml files in _data directory
-    Given I have a _data directory
-    And I have a "_data/members.yml" file with content:
-      """
-      - name: Jack
-        age: 28
-      - name: Leon
-        age: 34
-      """
-    And I have an "index.html" page that contains "{% for member in site.data.members %}{{member.name}}{% endfor %}"
-    When I run jekyll
-    Then the "_site/index.html" file should exist
-    And I should see "Jack" in "_site/index.html"
-    And I should see "Leon" in "_site/index.html"
-
-  Scenario: autoload *.yml files in _data directory with space in file name
-    Given I have a _data directory
-    And I have a "_data/team members.yml" file with content:
-      """
-      - name: Jack
-        age: 28
-      - name: Leon
-        age: 34
-      """
-    And I have an "index.html" page that contains "{% for member in site.data.team_members %}{{member.name}}{% endfor %}"
-    When I run jekyll
-    Then the "_site/index.html" file should exist
-    And I should see "Jack" in "_site/index.html"
-    And I should see "Leon" in "_site/index.html"
-
-  Scenario: should be backward compatible with site.data in _config.yml
-    Given I have a "_config.yml" file with content:
-      """
-      data:
-        - name: Jack
-          age: 28
-        - name: Leon
-          age: 34
-      """
-    And I have an "index.html" page that contains "{% for member in site.data %}{{member.name}}{% endfor %}"
-    When I run jekyll
-    Then the "_site/index.html" file should exist
-    And I should see "Jack" in "_site/index.html"
-    And I should see "Leon" in "_site/index.html"
-

data/lib/tigefa/entry_filter.rb

@@ -1,35 +0,0 @@
-class EntryFilter
-  attr_reader :site
-  def initialize(site)
-    @site = site
-  end
-
-  def filter(entries)
-    entries.reject do |e|
-      unless included?(e)
-        special?(e) || backup?(e) || excluded?(e) || symlink?(e)
-      end
-    end
-  end
-
-  def included?(entry)
-    site.include.glob_include?(entry)
-  end
-
-  def special?(entry)
-    ['.', '_', '#'].include?(entry[0..0])
-  end
-
-  def backup?(entry)
-    entry[-1..-1] == '~'
-  end
-
-  def excluded?(entry)
-    site.exclude.glob_include?(entry)
-  end
-
-  def symlink?(entry)
-    File.symlink?(entry) && site.safe
-  end
-
-end

data/site/_posts/2013-10-28-jekyll-1-3-0-rc1-released.markdown

@@ -1,19 +0,0 @@
----
-layout: news_item
-title: 'Jekyll 1.3.0.rc1 Released'
-date: 2013-10-28 20:14:39 -0500
-author: mattr-
-version: 1.3.0.rc1
-categories: [release]
----
-
-Jekyll 1.3.0 is going to be a big release! In order to make sure we
-didn't screw anything up too badly, we're making a release candidate
-available for any early adopters who want to give the latest and
-greatest code a spin without having to clone a repository from git.
-
-Please take this prerelease for a spin and [let us
-know](https://github.com/mojombo/jekyll/issues/new) if you run into any
-issues!
-
-

data/site/_posts/2013-11-04-jekyll-1-3-0-released.markdown

@@ -1,43 +0,0 @@
----
-layout: news_item
-title: 'Jekyll 1.3.0 Released'
-date: 2013-11-04 21:46:02 -0600
-author: mattr-
-version: 1.3.0
-categories: [release]
----
-
-It's been about six weeks since v1.2.0 and the Jekyll team is happy to
-announce the arrival of v1.3.0. This is a **huge** release full of all
-sorts of new features, bug fixes, and other things that you're sure to
-love.
-
-Here are a few things we think you'll want to know about this release:
-
-* You can add [arbitrary data][] to the site by adding YAML files under a
-  site's `_data` directory. This will allow you to avoid
-  repetition in your templates and to set site specific options without
-  changing `_config.yml`.
-
-* You can now run `jekyll serve --detach` to boot up a WEBrick server in the
-  background. **Note:** you'll need to run `kill [server_pid]` to shut
-  the server down. When ran, you'll get a process id that you can use in
-  place of `[server_pid]`
-
-* You can now **disable automatically-generated excerpts** if you set
-  `excerpt_separator` to `""`.
-
-* If you're moving pages and posts, you can now check for **URL
-  conflicts** by running `jekyll doctor`.
-
-* If you're a fan of the drafts feature, you'll be happy to know we've
-  added `-D`, a shortened version of `--drafts`.
-
-* Permalinks with special characters should now generate without errors.
-
-* Expose the current Jekyll version as the `jekyll.version` Liquid
-  variable.
-
-For a full run-down, visit our [change log](/docs/history/)!
-
-[arbitrary data]: /docs/datafiles/

data/site/_posts/2013-11-26-jekyll-1-3-1-released.markdown

@@ -1,21 +0,0 @@
----
-layout: news_item
-title: 'Jekyll 1.3.1 Released'
-date: 2013-11-26 19:52:20 -0600
-author: mattr-
-version: 1.3.1
-categories: [release]
----
-
-Just in time for the US holiday Thanksgiving, we're releasing version
-1.3.1 of Jekyll to address some of the issues seen since the
-release of 1.3.0.
-
-In addition to a couple of other smaller bug fixes, the biggest thing
-we've fixed is an issue with the `--watch` option with Ruby 1.8.7. For a
-full run-down, visit our [change log](/docs/history/)!
-
-Thanks to all the people who have contributed to this release! They are
-(in alphabetical order): Abhi Yerra, Anatol Broder, Andreas Möller, Greg
-Karékinian, Sam Rayner, Santeri Paavolainen, Shigeya Suzuki, Yihang Ho,
-albertogg, andrewhavens, maul.esel, and thomasdao

data/site/_posts/2013-12-07-jekyll-1-4-0-released.markdown

@@ -1,30 +0,0 @@
----
-layout: news_item
-title: 'Jekyll 1.4.0 Released'
-date: 2013-12-07 13:55:28 -0600
-author: mattr-
-version: 1.4.0
-categories: [release]
----
-
-About a month after the release of Jekyll v1.3.0, we are releasing
-Jekyll v1.4.0. This release will be the last non-patch release to support Ruby
-1.8.7 and our next release will be Jekyll 2.0.0.
-
-Here are a few things we think you'll want to know about this release:
-
-* TOML is now a supported markup language for config files.
-
-* Maruku has been updated to 0.7.0 which provides some new features and
-  a ton of bugfixes over the previous 0.6.x releases.
-
-* Non-`gem` Plugins are now sorted alphabetically by filename before they're
-  processed, which can provide a rudimentary way to establish a load order for
-  plugins.
-
-For a full run-down, visit our [change log](/docs/history/)!
-
-As always, Jekyll wouldn't be possible without the contributions from
-others in the Jekyll community. We'd like to thank the following people
-for contributing to this release: Anatol Broder, David Sawyer, Greg
-Karékinian, Jordon Bedwell, Matthew Iversen, Persa Zula, and Yi Zeng.

data/site/_posts/2013-12-16-jekyll-1-4-2-released.markdown

@@ -1,18 +0,0 @@
----
-layout: news_item
-title: 'Jekyll 1.4.2 Released'
-date: 2013-12-16 19:48:13 -0500
-author: parkr
-version: 1.4.2
-categories: [release]
----
-
-This release fixes [a regression][] where Maruku fenced code blocks were turned
-off, instead of the previous default to on. We've added a new default
-configuration to our `maruku` config key: `fenced_code_blocks` and set it to
-default to `true`.
-
-If you do not wish to use Maruku fenced code blocks, you may turn this option
-off in your site's configuration file.
-
-[a regression]: https://github.com/jekyll/jekyll/pull/1830

data/site/_posts/2014-01-13-jekyll-1-4-3-released.markdown

@@ -1,27 +0,0 @@
----
-layout: news_item
-title: 'Jekyll 1.4.3 Released'
-date: 2014-01-13 17:43:32 -0800
-author: benbalter
-version: 1.4.3
-categories: [release]
----
-
-Jekyll 1.4.3 contains two **critical** security fixes. If you run Jekyll locally
-and do not run Jekyll in "safe" mode (e.g. you do not build Jekyll sites on behalf
-of others), you are not affected and are not required to update at this time.
-([See pull request.]({{ site.repository }}/pull/1944))
-
-Versions of Jekyll prior to 1.4.3 and greater than 1.2.0 may allow malicious
-users to expose the content of files outside the source directory in the
-generated output via improper symlink sanitization, potentially resulting in an
-inadvertent information disclosure.
-
-Versions of Jekyll prior to 1.4.3 may also allow malicious users to write
-arbitrary `.html` files outside of the destination folder via relative path
-traversal, potentially overwriting otherwise-trusted content with arbitrary HTML
-or Javascript depending on your server's configuration.
-
-*Maintainer's note: Many thanks to @gregose and @charliesome for discovering
-these vulnerabilities, and to @BenBalter and @alindeman for writing the patch.
--@parkr*

data/site/docs/datafiles.md

@@ -1,63 +0,0 @@
----
-layout: docs
-title: Data Files
-prev_section: variables
-next_section: migrations
-permalink: /docs/datafiles/
----
-
-In addition to the [built-in variables](../variables/) available from Jekyll,
-you can specify your own custom data that can be accessed via the [Liquid 
-templating system](http://wiki.github.com/shopify/liquid/liquid-for-designers).
-
-Jekyll supports loading data from [YAML](http://yaml.org/) files located in the 
-`_data` directory.
-
-This powerful features allows you to avoid repetition in your templates and to
-set site specific options without changing `_config.yml`. 
-
-Plugins/themes can also leverage Data Files to set configuration variables.
-
-## The Data Folder
-
-As explained on the [directory structure](../structure/) page, the `_data` 
-folder is where you can store additional data for Jekyll to use when generating
-your site. These files must be YAML files (using either the `.yml` or `.yaml`
-extension) and they will be accessible via `site.data`.
-
-## Example: List of members
-
-Here is a basic example of using Data Files to avoid copy-pasting large chunks of
-code in your Jekyll templates:
-
-In `_data/members.yml`:
-
-{% highlight yaml %}
-- name: Tom Preston-Werner
-  github: mojombo
-
-- name: Parker Moore
-  github: parkr
-
-- name: Liu Fengyun
-  github: liufengyun
-{% endhighlight %}
-
-This data can be accessed via `site.data.members` (notice that the filename
-determines the variable name).
-
-You can now render the list of members in a template:
-
-{% highlight html %}
-{% raw %}
-<ul>
-{% for member in site.data.members %}
-  <li>
-    <a href="https://github.com/{{ member.github }}">
-      {{ member.name }}
-    </a>
-  </li>
-{% endfor %}
-</ul>
-{% endraw %}
-{% endhighlight %}

data/test/source/_config.dev.toml

@@ -1,2 +0,0 @@
-baseurl = "/you-beautiful-blog-you"
-title = "My magnificent site, wut"

data/test/source/_data/languages.yml

@@ -1,2 +0,0 @@
-- java
-- ruby

data/test/source/_data/members.yaml

@@ -1,7 +0,0 @@
-- name: Jack
-  age: 27
-  blog: http://example.com/jack
-
-- name: John
-  age: 32
-  blog: http://example.com/john

data/test/source/_data/products.yml

@@ -1 +0,0 @@
-../products.yml

data/test/source/_includes/tmp

@@ -1 +0,0 @@
-/tmp

data/test/source/_layouts/post/simple.html

@@ -1 +0,0 @@
-<<< {{ content }} >>>

data/test/source/_posts/2014-01-06-permalink-traversal.md

@@ -1,5 +0,0 @@
----
-permalink: /%2e%2e/%2e%2e/%2e%2e/baddie.html
----
-
-# Test

data/test/source/exploit.md

@@ -1,5 +0,0 @@
----
-permalink: /%2e%2e/%2e%2e/%2e%2e/baddie.html
----
-
-# Test

data/test/source/products.yml

@@ -1,4 +0,0 @@
-- name: sugar
-  price: 5.3
-- name: salt
-  price: 2.5

data/test/source/symlink-test/_data

@@ -1 +0,0 @@
-../_data

data/test/test_entry_filter.rb

@@ -1,74 +0,0 @@
-require 'helper'
-
-class TestEntryFilter < Test::Unit::TestCase
-  context "Filtering entries" do
-    setup do
-      stub(Tigefa).configuration do
-        Tigefa::Configuration::DEFAULTS.merge({'source' => source_dir, 'destination' => dest_dir})
-      end
-      @site = Site.new(Tigefa.configuration)
-    end
-
-    should "filter entries" do
-      ent1 = %w[foo.markdown bar.markdown baz.markdown #baz.markdown#
-              .baz.markdow foo.markdown~ .htaccess _posts _pages]
-
-      entries = EntryFilter.new(@site).filter(ent1)
-      assert_equal %w[foo.markdown bar.markdown baz.markdown .htaccess], entries
-    end
-
-    should "filter entries with exclude" do
-      excludes = %w[README TODO]
-      files = %w[index.html site.css .htaccess]
-
-      @site.exclude = excludes + ["exclude*"]
-      assert_equal files, @site.filter_entries(excludes + files + ["excludeA"])
-    end
-
-    should "not filter entries within include" do
-      includes = %w[_index.html .htaccess include*]
-      files = %w[index.html _index.html .htaccess includeA]
-
-      @site.include = includes
-      assert_equal files, @site.filter_entries(files)
-    end
-
-    should "filter symlink entries when safe mode enabled" do
-      stub(Tigefa).configuration do
-        Tigefa::Configuration::DEFAULTS.merge({'source' => source_dir, 'destination' => dest_dir, 'safe' => true})
-      end
-      site = Site.new(Tigefa.configuration)
-      stub(File).symlink?('symlink.js') {true}
-      files = %w[symlink.js]
-      assert_equal [], site.filter_entries(files)
-    end
-
-    should "not filter symlink entries when safe mode disabled" do
-      stub(File).symlink?('symlink.js') {true}
-      files = %w[symlink.js]
-      assert_equal files, @site.filter_entries(files)
-    end
-
-    should "not include symlinks in safe mode" do
-      stub(Tigefa).configuration do
-        Tigefa::Configuration::DEFAULTS.merge({'source' => source_dir, 'destination' => dest_dir, 'safe' => true})
-      end
-      site = Site.new(Tigefa.configuration)
-
-      site.read_directories("symlink-test")
-      assert_equal [], site.pages
-      assert_equal [], site.static_files
-    end
-
-    should "include symlinks in unsafe mode" do
-      stub(Tigefa).configuration do
-        Tigefa::Configuration::DEFAULTS.merge({'source' => source_dir, 'destination' => dest_dir, 'safe' => false})
-      end
-      site = Site.new(Tigefa.configuration)
-
-      site.read_directories("symlink-test")
-      assert_not_equal [], site.pages
-      assert_not_equal [], site.static_files
-    end
-  end
-end