bunto-redirect-from 5.0.0 → 6.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: bc7bb4ce86c73a11425638bd50f9a0d249b8a050
-  data.tar.gz: 271cacd16af6faafccb38cfde32b87f15957b45c
+  metadata.gz: 9c81ffd0d28d8a47a8da2c647791c84c85940d89
+  data.tar.gz: 1e0d348db8ed13e868ce2a1c2f0b5cd509c48eae
 SHA512:
-  metadata.gz: f4f5ae05baf686bd599af05021c00e38929f902090b69af567a172a5b63a654f96d8a4dd2bff3e9c095cd3b9532f6ceb9ace8689c8b613a0ebc874a9e0c7c951
-  data.tar.gz: 2cd534a2e5488657de90885fe2a29f39286a903eda95157fee3a19ffdd03b6a031e61aebbb0d7f9f312d7dd53cf0a730aabccfb8a9e5885eec4a5d5fb1d812b0
+  metadata.gz: d7ca1612fb32ac2e0f4d39966721c7236f055e61f8dbf18f06bc4a684739f0f2aec9c7aa7e2318e0fcc29d26e1cecb4409035f5c1e5cfedd5c1498360e538d68
+  data.tar.gz: f8acb181e8a0431427c7cdfb3a336f332abe03528797ad9fb327e7fb35c225d5c55a7fb4220db6175091a0647fcf311fce309f6e59de58401df4e2b2f0da3f9f

data/.gitignore

@@ -1,18 +1,18 @@
-*.gem
-*.rbc
-.bundle
-.config
-.yardoc
-Gemfile.lock
-InstalledFiles
-_yardoc
-coverage
-doc/
-lib/bundler/man
-pkg
-rdoc
-spec/reports
-spec/fixtures/.bunto-metadata
-test/tmp
-test/version_tmp
-tmp
+*.gem
+*.rbc
+.bundle
+.config
+.yardoc
+Gemfile.lock
+InstalledFiles
+_yardoc
+coverage
+doc/
+lib/bundler/man
+pkg
+rdoc
+spec/reports
+spec/fixtures/.bunto-metadata
+test/tmp
+test/version_tmp
+tmp

data/.rspec

@@ -1,2 +1,2 @@
---color
---format progress
+--color
+--format progress

data/.travis.yml

@@ -1,26 +1,26 @@
-language: ruby
-before_script: bundle update
-script: "script/cibuild"
-sudo: false
-cache: bundler
-
-matrix:
-  include:
-    - # GitHub Pages
-      rvm: 2.1.1
-      env: GH_PAGES=true
-    - # Ruby 1.9
-      rvm: 1.9
-      env: BUNTO_VERSION=1.0
-  allow_failures:
-    - env: GH_PAGES=true
-  fast_finish: true
-
-rvm:
-  - 2.2
-  - 2.1
-  - 2.0
-env:
-  - ""
-  - BUNTO_VERSION=2.0
-  - BUNTO_VERSION=1.0
+# Travis CI
+language: ruby
+before_script:
+  - chmod a+x script/bootstrap
+  - chmod a+x script/cibuild
+  - chmod a+x script/release
+  - chmod a+x script/test
+  - bundle update
+script: "script/cibuild"
+sudo: false
+cache: bundler
+
+matrix:
+  include:
+    - # Ruby 2.2.5
+      rvm: 2.2.5
+      env: BUNTO_VERSION=3.0.0
+  fast_finish: true
+
+rvm:
+- 2.3.1
+- 2.3.0
+env:
+  - ""
+  - BUNTO_VERSION=3.0.0
+  - BUNTO_VERSION=3.2.1

data/Gemfile

@@ -1,8 +1,8 @@
-source 'https://rubygems.org'
-gemspec
-
-if ENV["GH_PAGES"]
-  gem "github-pages"
-elsif ENV["BUNTO_VERSION"]
-  gem "bunto", "~> #{ENV["BUNTO_VERSION"]}"
-end
+source 'https://rubygems.org'
+gemspec
+
+if ENV["GH_PAGES"]
+  gem "github-pages"
+elsif ENV["BUNTO_VERSION"]
+  gem "bunto", "~> #{ENV["BUNTO_VERSION"]}"
+end

data/History.markdown

@@ -1,3 +1,4 @@
-## 1.0.0 / 2016-02-08
-
-* Birthday!
+## HEAD
+
+## 1.0.0 / 2016-02-08
+* Birthday!

data/LICENSE.txt

@@ -1,22 +1,22 @@
-Copyright (c) 2016-present Parker Moore
-
-MIT License
-
-Permission is hereby granted, free of charge, to any person obtaining
-a copy of this software and associated documentation files (the
-"Software"), to deal in the Software without restriction, including
-without limitation the rights to use, copy, modify, merge, publish,
-distribute, sublicense, and/or sell copies of the Software, and to
-permit persons to whom the Software is furnished to do so, subject to
-the following conditions:
-
-The above copyright notice and this permission notice shall be
-included in all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
-NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
-LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
-OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
-WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+Copyright (c) 2016-present Parker Moore
+
+MIT License
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -1,128 +1,129 @@
-# BuntoRedirectFrom
-
-Give your Bunto posts and pages multiple URLs.
-
-When importing your posts and pages from, say, Tumblr, it's annoying and
-impractical to create new pages in the proper subdirectories so they, e.g.
-`/post/123456789/my-slug-that-is-often-incompl`, redirect to the new post URL.
-
-Instead of dealing with maintaining those pages for redirection, let
-`bunto-redirect-from` handle it for you.
-
-[![Build Status](https://travis-ci.org/bunto/bunto-redirect-from.svg?branch=master)](https://travis-ci.org/bunto/bunto-redirect-from)
-
-## How it Works
-
-Redirects are performed by serving an HTML file with an HTTP-REFRESH meta
-tag which points to your destination. No `.htaccess` file, nginx conf, xml
-file, or anything else will be generated. It simply creates HTML files.
-
-## Installation
-
-Add this line to your application's Gemfile:
-
-    gem 'bunto-redirect-from'
-
-And then execute:
-
-    $ bundle
-
-Or install it yourself as:
-
-    $ gem install bunto-redirect-from
-
-Once it's installed into your evironment, add it to your `_config.yml`:
-
-```yaml
-gems:
-  - bunto-redirect-from
-```
-
-If you're using Bunto in `safe` mode to mimic GitHub Pages, make sure to
-add bunto-redirect-from to your whitelist:
-
-```yaml
-whitelist:
-  - bunto-redirect-from
-```
-
-Then run `bunto <cmd> --safe` like normal.
-
-## Usage
-
-The object of this gem is to allow an author to specify multiple URLs for a
-page, such that the alternative URLs redirect to the new Bunto URL.
-
-To use it, simply add the array to the YAML front-matter of your page or post:
-
-```yaml
-title: My amazing post
-redirect_from:
-  - /post/123456789/
-  - /post/123456789/my-amazing-post/
-```
-
-Redirects including a trailing slash will generate a corresponding subdirectory containing an `index.html`, while redirects without a trailing slash will generate a corresponding `filename` without an extension, and without a subdirectory.
-
-For example...
-
-```text
-redirect_from:
-  - /post/123456789/my-amazing-post
-```
-
-...will generate the following page in the destination:
-
-```text
-/post/123456789/my-amazing-post
-```
-
-While...
-
-```text
-redirect_from:
-  - /post/123456789/my-amazing-post/
-```
-
-...will generate the following page in the destination:
-
-```text
-/post/123456789/my-amazing-post/index.html
-```
-
-These pages will contain an HTTP-REFRESH meta tag which redirect to your URL.
-
-You can also specify just **one url** like this:
-
-```text
-title: My other awesome post
-redirect_from: /post/123456798/
-```
-
-### Prefix
-If `site.baseurl` is set, its value is used as a prefix for the redirect url automatically.
-This is useful for scenarios where a site isn't available from the domain root, so the redirects point to the correct path.
-
-**_Note_**: If you are hosting your Bunto site on [GitHub Pages](https://pages.github.com/), the prefix is set to the pages domain name i.e. `http://example.github.io/project` or a custom `CNAME`.
-
-### Redirect To
-
-Sometimes, you may want to redirect a site page to a totally different website. This plugin also supports that with the `redirect_to` key:
-
-```yaml
-title: My amazing post
-redirect_to:
-  - http://www.github.com
-```
-
-If you have multiple `redirect_to`s set, only the first one will be respected.
-
-**Note**: if using `redirect_to` with collections, your collection's extension **must** end in *.html* in order for `redirect_to` to properly process.
-
-## Contributing
-
-1. Fork it
-2. Create your feature branch (`git checkout -b my-new-feature`)
-3. Commit your changes (`git commit -am 'Add some feature'`)
-4. Push to the branch (`git push origin my-new-feature`)
-5. Create new Pull Request
+# BuntoRedirectFrom
+
+Give your Bunto posts and pages multiple URLs.
+
+When importing your posts and pages from, say, Tumblr, it's annoying and
+impractical to create new pages in the proper subdirectories so they, e.g.
+`/post/123456789/my-slug-that-is-often-incompl`, redirect to the new post URL.
+
+Instead of dealing with maintaining those pages for redirection, let
+`bunto-redirect-from` handle it for you.
+
+[![Build Status](https://travis-ci.org/bunto/bunto-redirect-from.svg?branch=master)](https://travis-ci.org/bunto/bunto-redirect-from)
+
+## How it Works
+
+Redirects are performed by serving an HTML file with an HTTP-REFRESH meta
+tag which points to your destination. No `.htaccess` file, nginx conf, xml
+file, or anything else will be generated. It simply creates HTML files.
+
+## Installation
+
+Add this line to your application's Gemfile:
+
+    gem 'bunto-redirect-from'
+
+And then execute:
+
+    $ bundle
+
+Or install it yourself as:
+
+    $ gem install bunto-redirect-from
+
+Once it's installed into your evironment, add it to your `_config.yml`:
+
+```yaml
+gems:
+  - bunto-redirect-from
+```
+
+If you're using Bunto in `safe` mode to mimic GitHub Pages, make sure to
+add bunto-redirect-from to your whitelist:
+
+```yaml
+whitelist:
+  - bunto-redirect-from
+```
+
+Then run `bunto <cmd> --safe` like normal.
+
+## Usage
+
+The object of this gem is to allow an author to specify multiple URLs for a
+page, such that the alternative URLs redirect to the new Bunto URL.
+
+To use it, simply add the array to the YAML front-matter of your page or post:
+
+```yaml
+title: My amazing post
+redirect_from:
+  - /post/123456789/
+  - /post/123456789/my-amazing-post/
+```
+
+Redirects including a trailing slash will generate a corresponding subdirectory containing an `index.html`, while redirects without a trailing slash will generate a corresponding `filename` without an extension, and without a subdirectory.
+
+For example...
+
+```text
+redirect_from:
+  - /post/123456789/my-amazing-post
+```
+
+...will generate the following page in the destination:
+
+```text
+/post/123456789/my-amazing-post
+```
+
+While...
+
+```text
+redirect_from:
+  - /post/123456789/my-amazing-post/
+```
+
+...will generate the following page in the destination:
+
+```text
+/post/123456789/my-amazing-post/index.html
+```
+
+These pages will contain an HTTP-REFRESH meta tag which redirect to your URL.
+
+You can also specify just **one url** like this:
+
+```text
+title: My other awesome post
+redirect_from: /post/123456798/
+```
+
+### Prefix
+If `site.baseurl` is set, its value is used as a prefix for the redirect url automatically.
+This is useful for scenarios where a site isn't available from the domain root, so the redirects point to the correct path.
+
+**_Note_**: If you are hosting your Bunto site on [GitHub Pages](https://pages.github.com/), the prefix is set to the pages domain name i.e. `http://example.github.io/project` or a custom `CNAME`.
+
+### Redirect To
+
+Sometimes, you may want to redirect a site page to a totally different website. This plugin also supports that with the `redirect_to` key:
+
+```yaml
+title: My amazing post
+redirect_to:
+  - http://www.github.com
+```
+
+If you have multiple `redirect_to`s set, only the first one will be respected.
+
+
+**Note**: Using `redirect_to` or `redirect_from` with collections will only work with files which are output to HTML, such as `.md`, `.textile`, `.html` etc.
+
+## Contributing
+
+1. Fork it
+2. Create your feature branch (`git checkout -b my-new-feature`)
+3. Commit your changes (`git commit -am 'Add some feature'`)
+4. Push to the branch (`git push origin my-new-feature`)
+5. Create new Pull Request

data/Rakefile

@@ -1,6 +1,6 @@
-require "bundler/gem_tasks"
-require 'rspec/core/rake_task'
-
-RSpec::Core::RakeTask.new(:spec)
-
-task :default => :spec
+require "bundler/gem_tasks"
+require 'rspec/core/rake_task'
+
+RSpec::Core::RakeTask.new(:spec)
+
+task :default => :spec