padrino-core 0.13.3.2 → 0.13.3.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: c520f17025850cb73e09a637eb0cd8ab8565dd35
-  data.tar.gz: ea7853c7622e65cda595072d8ba4934260938463
+  metadata.gz: 26b8e13eba532572139380b2f6a88d803f8a383b
+  data.tar.gz: 5a25cb854c9d8831248d33b300bea051e8b331b1
 SHA512:
-  metadata.gz: 2fc4d76ef3cb98fe74e7ec1c80fc6943df00d34482d29bf2a41daf910a75b47de5e30efd9a31e8e433d8dd1d4211d9fafc3aecce9fe9d35729ba59c730af37a2
-  data.tar.gz: 47c49980091e206fb860533e9e7a23d6c17819768f14b15656d5ee8b67f4c586fea2e5b8514a330fb5052f60cdda4593f9cc1c4947e0b107b756fbd9e24e1628
+  metadata.gz: 735507da932437fe46cf349e41af613b013aec13a3845a92b71437d47275ac6426409811a18c079be687e149830ab77c77dcdbdd3c00c24cd5d98a4015d6d75c
+  data.tar.gz: 0c2493807fb6fac6d6a810d9c99d18f1baa9a27eb39c5babf3ebb3ba2f1a4cef3c6be05850b201aedda7e25f76b1092c58a9742e8aaec1b1d7d3b64f857a8684

data/README.rdoc

@@ -34,7 +34,7 @@ Reloading:: Automatically reloads server code during development.
 Localization:: Full support of I18n language localization and can auto-set user's locale.
 
 Keep in mind, the user will be able to pull in these components
-{seperately into existing Sinatra applications}[http://www.padrinorb.com/guides/standalone-usage-in-sinatra]
+{seperately into existing Sinatra applications}[http://padrinorb.com/guides/advanced-usage/standalone-usage-in-sinatra/]
 or use them altogether for a comprehensive upgrade to Sinatra (a full-stack Padrino application).
 
 == Installation
@@ -47,7 +47,7 @@ This will install the necessary padrino gems to get you started.
 Now you are ready to use this gem to enhance your sinatra projects or to create new Padrino applications.
 
 For a more detailed look at Padrino installation,
-check out the {Installation Guide}[http://www.padrinorb.com/guides/installation].
+check out the {Installation Guide}[http://padrinorb.com/guides/getting-started/installation/].
 
 == Usage
 
@@ -57,20 +57,20 @@ on the enhancements to the core Sinatra functionality. To use Padrino, one shoul
 usage of Sinatra itself.
 
 Please check out the
-{Understanding Sinatra}[http://www.padrinorb.com/guides/underlying-sinatra-overview] guide
+{Understanding Sinatra}[http://padrinorb.com/guides/introduction/why-learn-padrino/#learning-to-love-sinatra] guide
 to learn more about these fundamentals.
 
 For information on how to use a specific gem in isolation within an existing Sinatra project, checkout the guide for
-{Using Padrino in Sinatra}[http://www.padrinorb.com/guides/standalone-usage-in-sinatra].
+{Using Padrino in Sinatra}[http://padrinorb.com/guides/advanced-usage/standalone-usage-in-sinatra/].
 
 == Getting Started
 
 Once a developer understands Sinatra, Padrino is quite easy to get comfortable with since Padrino is simply a superset
 of existing Sinatra Functionality! Best way to get started with building Padrino applications is to read following resources:
 
-* {Blog Tutorial}[http://www.padrinorb.com/guides/blog-tutorial] - Step-by-step guide to building a blog application with Padrino.
-* {Quick Overview}[http://www.padrinorb.com/guides/basic-projects] - Outlines basic generation commands.
-* {Padrino Examples}[http://www.padrinorb.com/guides/examples] - List of known Padrino applications which can serve as examples.
+* {Blog Tutorial}[http://padrinorb.com/guides/getting-started/blog-tutorial/] - Step-by-step guide to building a blog application with Padrino.
+* {Quick Overview}[http://padrinorb.com/guides/getting-started/basic-projects/] - Outlines basic generation commands.
+* {Padrino Examples}[http://padrinorb.com/guides/introduction/examples/] - List of known Padrino applications which can serve as examples.
 
 == Enhanced Base Application (padrino-core)
 
@@ -104,10 +104,10 @@ Let us first take a look at the simplest possible Padrino application:
     end
   end
 
-=== Enhanced Route Definitions and Controllers
-
 For a complete overview of the Padrino routing and controller system,
-check out the {Routing and Controller guide}[http://www.padrinorb.com/guides/controllers].
+check out the {Routing and Controller guide}[http://padrinorb.com/guides/controllers/overview/].
+
+=== Enhanced Route Definitions and Controllers
 
 Suppose we wanted to add additional routes to our Padrino application, and we want to organize the routes
 within a more structured layout. Simply add a <tt>controllers</tt> or <tt>app/controllers</tt> folder and create a file as such:
@@ -175,7 +175,7 @@ When you visit :+show+ and your I18n.locale == :ru Padrino try to look for "admi
 they try "admin/show.ru.*" then "admin/show.js.*" if none match return "admin/show.erb" (or other engine i.e. haml)
 
 For a complete overview of the routing and controller system, check out the
-{Routing and Controller guide}[http://www.padrinorb.com/guides/controllers].
+{Routing and Controller guide}[http://padrinorb.com/guides/controllers/overview/].
 
 === Rendering
 
@@ -191,7 +191,7 @@ The existing render function works as well if an engine type should be specified
 render :haml, 'account/index'
 
 For a complete overview of the Padrino rendering system, check out the
-{Routing and Controller guide}[http://www.padrinorb.com/guides/controllers].
+{Routing and Controller guide}[http://padrinorb.com/guides/controllers/rendering/].
 
 === Layout
 
@@ -206,7 +206,7 @@ With Padrino you can (like rails do) use for your custom layout, disable it
     layout :custom
 
 For a complete overview of the layout functionality,
-check out the {Routing and Controller guide}[http://www.padrinorb.com/guides/controllers].
+check out the {Routing and Controller guide}[http://padrinorb.com/guides/controllers/layouts/].
 
 === Mounting Applications
 
@@ -221,7 +221,7 @@ Padrino stores application mounting information by default within <tt>config/app
 to keep all information regarding what applications are mounted to which uri's.
 
 For a complete look at mounting applications within a Padrino project,
-check out the guide on {Mounting Applications}[http://www.padrinorb.com/guides/mounting-applications].
+check out the guide on {Mounting Applications}[http://padrinorb.com/guides/features/mounting-applications/].
 
 === Auto Load Paths
 
@@ -231,7 +231,7 @@ as a convention for establishing database connection. Also, any files within the
 automatically by Padrino.
 
 For a complete overview of auto-loaded paths within Padrino,
-check out the {Padrino Development Guide}[http://www.padrinorb.com/guides/development-and-terminal-commands].
+check out the {Padrino Development Guide}[http://padrinorb.com/guides/features/development-commands/#auto-load-paths].
 
 === Application Logging
 
@@ -248,7 +248,7 @@ within your app and any controller or views:
   end
 
 For a complete overview of Padrino logger functionality, check out the
-{Padrino Development Guide}[http://www.padrinorb.com/guides/development-and-terminal-commands].
+{Padrino Development Guide}[http://padrinorb.com/guides/features/development-commands/].
 
 === Development Reloader
 
@@ -260,7 +260,7 @@ This makes rapid development much easier and provides a better alternative to 's
 which requires the application server to be restarted which makes requests take much longer to complete.
 
 For a complete overview of code reloading in development,
-check out the {Padrino Development Guide}[http://www.padrinorb.com/guides/development-and-terminal-commands].
+check out the {Padrino Development Guide}[http://padrinorb.com/guides/features/development-commands/#development-reloader].
 
 === Terminal Commands
 
@@ -287,7 +287,7 @@ You can also create custom rake tasks as well. Using these commands can simplify
 making development that much smoother.
 
 For a complete overview of Padrino terminal commands, check out the
-{Padrino Commands Guide}[http://www.padrinorb.com/guides/development-and-terminal-commands].
+{Padrino Commands Guide}[http://padrinorb.com/guides/features/development-commands/#terminal-commands].
 
 == Copyright
 

data/lib/padrino-core/application/routing.rb

@@ -214,7 +214,7 @@ module Padrino
       #   before :agent => /IE/ do; ...; end
       #   # => match +HTTP_USER_AGENT+ containing +IE+
       #
-      # @see http://www.padrinorb.com/guides/controllers#route-filters
+      # @see http://padrinorb.com/guides/controllers/route-filters/
       #
       def construct_filter(*args, &block)
         options = args.last.is_a?(Hash) ? args.pop : {}

data/lib/padrino-core/version.rb

@@ -6,7 +6,7 @@
 #
 module Padrino
   # The version constant for the current version of Padrino.
-  VERSION = '0.13.3.2' unless defined?(Padrino::VERSION)
+  VERSION = '0.13.3.3' unless defined?(Padrino::VERSION)
 
   #
   # The current Padrino version.

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: padrino-core
 version: !ruby/object:Gem::Version
-  version: 0.13.3.2
+  version: 0.13.3.3
 platform: ruby
 authors:
 - Padrino Team
@@ -11,7 +11,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2016-09-06 00:00:00.000000000 Z
+date: 2016-11-02 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: padrino-support
@@ -19,14 +19,14 @@ dependencies:
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 0.13.3.2
+        version: 0.13.3.3
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 0.13.3.2
+        version: 0.13.3.3
 - !ruby/object:Gem::Dependency
   name: sinatra
   requirement: !ruby/object:Gem::Requirement
@@ -238,7 +238,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: 1.3.6
 requirements: []
 rubyforge_project: padrino-core
-rubygems_version: 2.5.1
+rubygems_version: 2.6.6
 signing_key: 
 specification_version: 4
 summary: The required Padrino core gem