exception_handler 0.3.45 → 0.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: f2138c87ceb274a814a29d092734aa1a69803fb1
-  data.tar.gz: 2e88d2a0b3712594ba8cca9f54fd0aa1c2e17e36
+  metadata.gz: 59b626c88f86b2004ac659f93be9a15249db6809
+  data.tar.gz: 13a0cd232e3e096df48e6afe04a1a43ebe5de56d
 SHA512:
-  metadata.gz: d50d274eafdc3b0cc3ff5eb0d8e8056b06ee7cebcc1251b4e01c155cce28080c438fb7ba523a82664a93c42cfe415194b41e4b0cc3a89cced0fb390d67acf545
-  data.tar.gz: a49b192481e227188d0d60f1a44e9d0acf9e1c6cdee824b4fb10a21583f26fea45ca50ff489c68fff0c1c69ff922f6ed618c2d61811d22d07ddd3830fcc6aa52
+  metadata.gz: a9112518dc66d6f03981325fe72437c7365f748802bb39c562e8185ad15234e9a091a4f09247c8bcd4bd4b4bb1984de67adb4857981c35ff68ed6f61c48a04e3
+  data.tar.gz: 62328b6458cd677c0ff16646a2dcd68449afa5284ab50fc93486989b558d79331b35ffb5773bd04b4cc8ddc66dfbc1175a0d627f62c56ef19a4466a0089b8f1f

data/README.md

@@ -1,4 +1,4 @@
-# [![Exception Handler](https://raw.githubusercontent.com/richpeck/exception_handler/master/readme/exception_handler.png "Exception Handler Logo")](http://frontlineutilities.co.uk/ruby-on-rails/exception-handler)
+![Exception Handler](/readme/title.png "Exception Handler Logo")
 
 [![Gem Version](https://badge.fury.io/rb/exception_handler.svg)](http://badge.fury.io/rb/exception_handler)
 [![Code Climate](https://codeclimate.com/github/richpeck/exception_handler.png)](https://codeclimate.com/github/richpeck/exception_handler)
@@ -7,205 +7,169 @@
 [![Build Status](https://travis-ci.org/richpeck/exception_handler.svg?branch=master)](https://travis-ci.org/richpeck/exception_handler)
 
 
-[**ExceptionHandler** Rails Gem](https://rubygems.org/gems/exception_handler) (adapted from [this tutorial](https://gist.github.com/wojtha/8433843) & [this tutorial](http://www.sharagoz.com/posts/1-rolling-your-own-exception-handler-in-rails-3))
+----------
 
-Works with the [`config.exceptions_app`](http://guides.rubyonrails.org/configuring.html#rails-general-configuration) hook in Rails' middleware stack:
+Sick of the standard Rails error pages?
 
-    config.exceptions_app sets the exceptions application invoked by the ShowExceptionmiddleware
-    when an exception happens. Defaults to ActionDispatch::PublicExceptions.new(Rails.public_path).
+Need a custom layout to show professional-looking errors in production?
 
------------
+`exception_handler` is exactly what you need!
 
-####Custom Error Pages
+----------
 
-`ExceptionHandler` deploys *custom error pages*. These allow you to serve your own design error pages in production; showing both the error, and the problem. This is a big step forward from the standard Rails error reporting facility
+**ExceptionHandler** provides error handling for Rails 4+ apps *(adapted from [**1**](https://gist.github.com/wojtha/8433843) & [**2**](http://www.sharagoz.com/posts/1-rolling-your-own-exception-handler-in-rails-3))*.
 
-There are two types of error page: 
+It hooks into the **[`config.exceptions_app`](http://guides.rubyonrails.org/configuring.html#rails-general-configuration)** middleware:
 
-	- 404 errors
-	- 500 errors (+ other)
+![Exceptions_App middleware](/readme/exceptions_app.png)
 
-The custom **`404`** error uses your own `layout`. The **`500 & other errors`** are `server` issues, and so we have included an `errors` layout (`/views/layouts/errors.html.erb`).
+With **ExceptionHandler**, you can create custom **404 & 500 production error pages**:
 
-The `errors` layout in important. If you try and load your "standard" layout with an internal server error, all your
-"supporting" functionality is called too. Problem? You're likely going to cause even more errors.
+![Exceptions_App middleware](/readme/subtitle.jpg)
 
-**Custom error pages** are included by default.
-You can change them by using the **`rails generate exception_handler:assets --views`**:
+---
 
- **500 Errors** | **404 Errors**
---- | ---
-![500 Server Error Pages](https://raw.githubusercontent.com/richpeck/exception_handler/master/readme/500.png "500 Server Error Page") | ![404 Server Error Pages](https://raw.githubusercontent.com/richpeck/exception_handler/master/readme/404.png "404 Server Error Page") 
-Uses **errors** layout | Uses **standard** layout
-
------------
-
-####Saving Errors To DB
-
-Adapted & refactored from [this tutorial](http://www.sharagoz.com/posts/1-rolling-your-own-exception-handler-in-rails-3)
-
-Sometimes, you want to save your errors to your database (admin areas, multi-tenant apps, etc). We've included some middleware which captures the exceptions & saves them to the db:
-
-	- Model (class) Name
-	- Error Message
-	- Stack trace
-	- Target URL
-	- Referrer URL
-	- Params
-	- User Agent (Browser Details)
+**ExceptionHandler** catches errors in the middleware hook (`config.exceptions_app`), channeling the users to our [custom `exceptions` controller](blob/master/app/controllers/exception_handler/exception_controller.rb). It then dissects data such as the `message`, `details`, `user agent`, etc, redirect the user to a `custom view`, storing it in the db:
 
-This db allows you to track, read & repair errors in your application on the fly. We deploy this in our admin areas, to help us
-appreciate any issues on our client apps.
+**40x Errors** | **50x Errors**
+--- | ---
+![404 Error Page](/readme/400.jpg "404 Error Page (Uses Application Layout)") | ![500 Error Page](/readme/500.jpg "500 Error Page (Uses Error Layout)") 
+**layouts/application.html.erb** | **layouts/errors.html.erb** 
 
-![Errors Table](https://raw.githubusercontent.com/richpeck/exception_handler/master/readme/db.png "Errors Table")
 
-This functionality is **`disabled`** by default
+All exceptions in Rails are handled by the [`ActiveDispatch::ShowExceptions`](https://github.com/rails/rails/blob/4-0-stable/actionpack/lib/action_dispatch/middleware/show_exceptions.rb) middleware. 
 
-To enable, you need to do the following:
+This is invoked through a hook called `config.exceptions_app`, accessed through the `environment` files of rails `application.rb`, `environments/development.rb`, `environments/production.rb` etc.
 
-	- rails generate exception_handler:install #-> will install config initializer
-	- rails generate exception_handler:migration #-> will create migration (for `errors` table)
-	- rake db:migrate #-> creates `errors` table
+Whilst it's common practice to use `config.exceptions_app = self.routes` to send exceptions to your routes, `ExceptionHandler` hooks directly into the middleware, giving us access to all the data:
 
-	- config/initializers/exception_handler.rb
-	- ExceptionHandler.setup do |config|
-	-    config.db = true
-	- end
+![Parse](/readme/parser.jpg "Parser")
 
----------
+----------
 
 ## Installation
 
-###Step1 
-
-You need to reference the [`exception_handler`](http://rubygems.org/gems/exception_handler) gem. Once you have downloaded the gem, you'll be able to deploy it in your application.
-
-Add this line to your application's Gemfile:
+     gem install 'exception_handler'
+ 
+or 
 
-	gem 'exception_handler'
-
-And then execute:
+    gem 'exception_handler', '~> 0.4' # Gemfile
 
     $ bundle
 
-**Or** install it yourself as:
-
-    $ gem install exception_handler
-
-![gem install](https://raw.githubusercontent.com/richpeck/exception_handler/master/readme/gem_install.png "gem install")
+You can see [`ExceptionHandler` on RubyGems](https://rubygems.org/gems/exception_handler)
 
 --
 
-###Step2
-
-Run:
+##### Config
 
-	rails generate exception_handler:install
+*Optional*
 
-![Installation](https://raw.githubusercontent.com/richpeck/exception_handler/master/readme/install.png "Installation")
+If you wish to change any of the default settings (listed below), run the following command:
 
-This will create `config/initializers/exception_handler.rb`. Whilst not vital, it will give you 
-access to the configuration options which can change the gem's behavior:
+    $ rails g exception_handler:install
 
-![Config File](https://raw.githubusercontent.com/richpeck/exception_handler/master/readme/config.png "Configuration")
+![Creates config/initializers/exception_handler.rb](/readme/config.jpg)
 
---
+This will deploy a file to `config/initializers/exception_handler.rb`, which you'll be able to edit as required.
 
-###Database
+You can run `ExceptionHandler` just from the `gem` if you wish.
 
-If you want to set up the database, you will need to use the `migration installer`:
+--
 
-	$ rails generate exception_handler:migration
+##### DB
 
-This creates:
+*Optional*
 
-	$ rake db:migrate
+If you want to set up database support (IE have exceptions saved to a table), you need to create a migration:
 
-This will migrate the datatable for you. Now you need to change `config.db = true`
+    $ rails generate exception_handler:migration
+    $ rake db:migrate
 
-![DB Config](https://raw.githubusercontent.com/richpeck/exception_handler/master/readme/config_db.png "Config DB")
+![Database](/readme/db.jpg "Database")
 
+This is an optional step. If you want to save the data, you will also need to ensure your `config.db` option is correct:
 
----------
+![Database Edit](/readme/db_edit.jpg "Database Edit")
 
-###Configuration
+--
 
-[Exception handler](https://rubygems.org/gems/exception_handler) comes with 3 installers
+##### Views
 
-**You only need to use `rails generate exception_handler:install`**. The others allow you to include files on your system, or create the `errors` table.
+*Optional*
 
-	# General
-	$ rails generate exception_handler:install #-> installs "config" file (initializer)
+If you want to change the views, you can have them put into your app:
 
-![Install](https://raw.githubusercontent.com/richpeck/exception_handler/master/readme/install.png "Standard Install")
+    $ rails generate exception_handler:views #-> controller, models, views & assets
+	$ rails generate exception_handler:views -v views controllers models assets #-> remove as appropriate to install individual assets
 
+The views will be appended to your app, and you'll be able to edit them as required.
 
-	# Migration
-	$ rails generate exception_handler:migration #-> generates migration for "errors" table
+---
 
-![Migration Install](https://raw.githubusercontent.com/richpeck/exception_handler/master/readme/install_migration.png "Migration Install")
+###### Show
 
+![View](/readme/view.jpg "View")
 
-	# Files
-	$ rails generate exception_handler:views #-> controller, models, views & assets
-	$ rails generate exception_handler:views -v views controllers models assets #-> remove as appropriate to install individual assets
+The view is located in `app/views/exception_handler/show.html.erb` designed to work for all exceptions.
 
-![Views Install](https://raw.githubusercontent.com/richpeck/exception_handler/master/readme/install_views.png "Views Install")
+By default, it is split for use with different layouts, data being available to both.
 
+This works exactly the same as the other views in your app (IE the `exceptions` controller invokes the `show` action)
 
+---
 
----------
+###### Layout
 
-## Usage
+One of the most critial aspects of **ExceptionHandler** is the custom `Error` layout.
 
-###Development Environment
+If you want to change the layout (for 500 error pages), you need to use the following:
 
-**[`config.exceptions_app`](http://guides.rubyonrails.org/configuring.html#rails-general-configuration)** is only used in Rails' production environment. Therefore, if you wish to **test the gem in dev**,
-you'll need to make your app process requests as `production` for now. This is a temporary step, and will be
-resolved in a new version:
+![Layout](/readme/layout.jpg "Layout")
 
-	#config/environments/development.rb
-	config.consider_all_requests_local = false # true
+----------
 
-![Development Testing](https://raw.githubusercontent.com/richpeck/exception_handler/master/readme/development.png "Development Testing")
+### Development
 
-You should change this setting if you wish to test your styling in development mode. Please note **it should be temporary**
+`config.exceptions_app` is only used in Rails' **production** environment.
 
---
+If you wish to test the gem in dev, you'll need to make your app process requests as production for now. This is a temporary step, and will be resolved in a new version:
 
-###Production Environment
+![#config/environments/development.rb](/readme/dev.jpg "Developer Testing")
 
-    No action required
+You should change this setting if you wish to test your styling in development mode. It should be temporary (you need to change it back once you have it looking how you like)
 
----------
+### Usable_Type & Usable_ID
 
-###Demo
+----------
 
-**404 Error** | **500 Error**
-:---: | :---:
-[![404 Error Page](https://raw.githubusercontent.com/richpeck/exception_handler/master/readme/404_demo.png "404 Error Page Demo")](http://firststopcosmeticshop.co.uk/sdfsdf/sdf/sdfsdf) | [![500 Error Page](https://raw.githubusercontent.com/richpeck/exception_handler/master/readme/500_demo.png "500 Error Page Demo")](http://firststopcosmeticshop.co.uk/search/fasdfasdfasdfasdfasdf)
-[Link](http://firststopcosmeticshop.co.uk/sdfsdf/sdf/sdfsdf) | [Link](http://firststopcosmeticshop.co.uk/search/fasdfasdfasdfasdfasdf)
+## Bugs
 
+1. `ApplicationController`
 
---------
+   ![ApplicationController](/readme/application_controller.jpg "Application Controller")
+   
+   A significant issue exists in respect to the inheritance of `exceptions_controller`.
+   Our current version (`0.4`) inherits from the `ApplicationController`. This causes a problem for many applications.
 
-## Support
+   If you use any sort of `before_action` callback in your controller, especially to populate variables, this
+   will cause untold problems in your `exceptions_controller`. 
 
-If you need help, you may consider:
+   `500` errors are server faults; trying to get the server to call more data will simply not work. It causes
+   an exception loop, leading to catastrophic failure.
 
-1. Watching this [**video tutorial**](http://www.youtube.com/watch?v=Zo2vav3dYnY):
 
-   [![ExceptionHandler Update](http://img.youtube.com/vi/Zo2vav3dYnY/0.jpg)](http://www.youtube.com/watch?v=Zo2vav3dYnY)
-2. Read [**our tutorial**](http://google.com)
-3. Ask on [**StackOverflow**](http://stackoverflow.com)
-4. Go on the [**gem support page**](http://frontlineutilities.co.uk)
+## Support
 
----------
+ - Watch the video tutorial (soon)
+ - [Create an "issue"](https://github.com/richpeck/exception_handler/issues) 
+ - Contact support (soon)
+ - [Ask on StackOverflow](http://stackoverflow.com/questions/ask?tags=exception_handler&ruby_on_rails) 
 
-## Contributing
+## Contribution
 
 1. Fork it ( https://github.com/richpeck/exception_handler/fork )
 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 a new Pull Request
+5. Create a new Pull Request

data/app/assets/stylesheets/exception_handler/error.css.erb

@@ -0,0 +1,297 @@
+/* Vars */
+<% size 	= 20 %>
+<% opacity 	= 0.85 %>
+<% footer 	= 50 %>
+<% radius 	= 5 %>
+<% title_bg = "rgba(227,11,11,1)" %>
+
+
+/* Responsive */
+@media screen and (max-width: 950px) {
+	html 				{ background-size: cover !important; }
+	.container .error	{ width: 55% !important; }
+}
+
+/* Styling */
+*  { margin: 0; }
+html, body, .container { height: 100%; }
+html {
+	height: 100%;
+	background: #010008 url(<%= asset_url("exception_handler/bg.jpg") %>) top left no-repeat;
+	background-size: 100% 100%;
+}
+body {
+	font-family: Helvetica, Arial, Sans-Serif;
+	font-size: 14px;
+	text-transform: capitalize;
+}
+body:before,
+body:after {
+	content: "";
+	position: absolute;
+	top: 0;
+	left: 0;
+	width: 100%;
+	height: 100%;
+	z-index: 1000;
+}
+body:before{ background-image: url(<%=asset_url("exception_handler/noise.png") %>); background-repeat: repeat; }
+body:after{ background-image: url(<%=asset_url("exception_handler/bg_overlay.png") %>); background-repeat: no-repeat; }
+
+a { color: #fff; text-decoration: none; }
+a:hover { text-decoration: underline; }
+
+.container {
+	position: relative;
+	min-height: 100%;
+	overflow-y: hidden; /* Shouldn't need to have this */
+	margin-bottom: -<%= footer * 1.2 %>px;
+	z-index: 1100;
+}
+
+.container .error {
+	display: block;
+	margin: 10% auto 0;
+	width: 25%;
+	color: #000;
+	text-align: center;
+	overflow: hidden;
+	background: rgba(255,255,255,1);
+	border: 1px solid rgba(0,0,0,1);
+	border-radius: <%= radius %>px;
+
+	-moz-background-clip: padding;  
+	-webkit-background-clip: padding-box;
+	background-clip: padding-box;  
+
+	-webkit-transition: width 0.15s ease-in-out;
+	-moz-transition: 	width 0.15s ease-in-out;
+	-ms-transition: 	width 0.15s ease-in-out;
+	-o-transition: 		width 0.15s ease-in-out;
+	transition: 		width 0.15s ease-in-out;
+}
+
+.container .error img.alert {
+	display: block;
+	margin: 0 auto 20px auto;
+}
+
+.container .message > * { display: block; }
+.container .message .title {
+	display: block;
+	position: relative;
+	font-weight: bold;
+	font-size: 0.85em;
+	margin: 0;
+	color: rgba(255,255,255,1);
+	background: <%= title_bg %>;
+	padding: 12px 15px;
+	text-align: left;
+	text-shadow: 0px 1px 0px rgba(0,0,0,1);
+	overflow-y: hidden;
+
+	/* Permalink - use to edit and share this gradient: http://colorzilla.com/gradient-editor/#7a07ed+0,000000+100&amp;0+0,1+100 */
+	background: <%= title_bg %> -moz-linear-gradient(top,  rgba(227,11,11,0) 0%, rgba(0,0,0,0.4) 100%); /* FF3.6+ */
+	background: <%= title_bg %> -webkit-gradient(linear, left top, left bottom, color-stop(0%,rgba(227,11,11,0)), color-stop(100%,rgba(0,0,0,0.4))); /* Chrome,Safari4+ */
+	background: <%= title_bg %> -webkit-linear-gradient(top, rgba(227,11,11,0) 0%,rgba(0,0,0,0.4) 100%); /* Chrome10+,Safari5.1+ */
+	background: <%= title_bg %> -o-linear-gradient(top,  rgba(227,11,11,0) 0%,rgba(0,0,0,0.4) 100%); /* Opera 11.10+ */
+	background: <%= title_bg %> -ms-linear-gradient(top,  rgba(227,11,11,0) 0%,rgba(0,0,0,0.4) 100%); /* IE10+ */
+	background: <%= title_bg %> linear-gradient(to bottom,  rgba(227,11,11,0) 0%,rgba(0,0,0,0.4) 100%); /* W3C */
+	filter: progid:DXImageTransform.Microsoft.gradient( startColorstr='#007a07ed', endColorstr='#000000',GradientType=0 ); /* IE6-9 */
+}
+.container .message .title:before,
+.container .message .title:after {
+	position: absolute;
+	content: "";
+	width: 100%;
+	left: 0;
+}
+.container .message .title:before {
+	position: absolute;
+	content: "";
+	width: 100%;
+	left: 0;
+	height: 100%;
+	top: 0;
+	background: url(<%= asset_url("exception_handler/overlay.png") %>) repeat;
+	background-size: 100%;
+}
+.container .message .title:after  {
+	height: 1px;
+	background: rgba(255,255,255,0.1);
+	bottom: 0px;
+}
+.container .message .title a.close {
+	float: right;
+	position: relative;
+	top: 2px;
+	right: -2px;
+}
+.container .message .title a.close img {
+	width: 12px;
+
+	-webkit-transition: opacity 0.15s ease-in-out;
+	-moz-transition: 	opacity 0.15s ease-in-out;
+	-ms-transition: 	opacity 0.15s ease-in-out;
+	-o-transition: 		opacity 0.15s ease-in-out;
+	transition: 		opacity 0.15s ease-in-out;
+}
+.container .message .title a.close:hover img { opacity: 0.75; }
+
+
+
+.container .message .details {
+	position: relative;
+	margin: 0;
+	padding: 0;
+	height: 310px;
+	width: 100%;
+	background-image: url(<%= asset_url("exception_handler/alert.jpg") %>);
+	background-repeat: no-repeat;
+	background-size: cover;
+	background-position: center top;
+}
+.container .message .details:before,
+.container .message .details:after {
+	display: block;
+	content: "";
+	position: absolute;
+	left: 0;
+	top: 0;
+	width: 100%;
+	z-index: 1000;
+}
+.container .message .details:after {
+	height: 2px;
+
+	/* Permalink - use to edit and share this gradient: http://colorzilla.com/gradient-editor/#000000+0,000000+100&amp;1+0,0+100 */
+	background: -moz-linear-gradient(top,  rgba(0,0,0,0.485) 0%, rgba(0,0,0,0) 100%); /* FF3.6+ */
+	background: -webkit-gradient(linear, left top, left bottom, color-stop(0%,rgba(0,0,0,0.85)), color-stop(100%,rgba(0,0,0,0))); /* Chrome,Safari4+ */
+	background: -webkit-linear-gradient(top,  rgba(0,0,0,0.85) 0%,rgba(0,0,0,0) 100%); /* Chrome10+,Safari5.1+ */
+	background: -o-linear-gradient(top,  rgba(0,0,0,0.85) 0%,rgba(0,0,0,0) 100%); /* Opera 11.10+ */
+	background: -ms-linear-gradient(top,  rgba(0,0,0,0.85) 0%,rgba(0,0,0,0) 100%); /* IE10+ */
+	background: linear-gradient(to bottom,  rgba(0,0,0,0.85) 0%,rgba(0,0,0,0) 100%); /* W3C */
+	filter: progid:DXImageTransform.Microsoft.gradient( startColorstr='#000000', endColorstr='#00000000',GradientType=0 ); /* IE6-9 */
+
+}
+.container .message .details:before {
+	height: 100%;
+	outline-offset: -1px;
+	outline: 1px solid rgba(255,255,255,0.1);
+}
+.container .message .details img {
+	margin: 10% 0 0 0;
+	padding: 0;
+}
+.container .message .details .status {
+	position: absolute;
+	left: 0;
+	bottom: 0;
+	width: 100%;
+	color: #fff;
+	padding: 1em 15px;
+	font-size: 1.1em;
+	font-weight: bold;
+	background: rgba(0,0,0,0.5);
+	text-align: left;
+}
+
+.container .message .info {
+	display: block;
+	padding-top: 15px;
+	margin: auto;
+	font-size: 0.75em;
+	background: rgba(232,232,232,1);
+}
+.container .message .info > * {
+	display: block;
+	padding-left: 15px;
+	padding-right: 15px;
+}
+.container .message > .info h2 {
+	margin: 10px 0;
+	font-size: 1.75em;
+	text-align: left;
+}
+.container .message > .info .notification {
+	display: block;
+	position: relative;
+	clear: both;
+	margin: 20px 0 0;
+	padding-top: 5px;
+	padding-bottom: 5px;
+	text-align: left;
+	background: rgba(205,205,205,1);
+	border-top: 1px solid rgba(175,175,175,1);
+}
+.container .message > .info .notification > * 	 { vertical-align: middle; }
+.container .message > .info .notification strong {
+	display: inline-block;
+	max-width: 75%;
+	text-overflow: ellipsis;
+	white-space: nowrap;
+	overflow-x: hidden;
+}
+.container .message > .info .notification .version {
+	display: inline-block;
+	text-transform: lowercase;
+	padding: 0 15px 0 0;
+	margin: 0 10px 0 0;
+	border-right: 1px solid rgba(175,175,175,1);
+}
+.container .message > .info .notification a.home {
+	float: right;
+	position: relative;
+	right: -6px;
+	opacity: <%= opacity * 0.5 %>;
+
+	-webkit-transition: opacity 0.15s ease-in-out;
+	-moz-transition: 	opacity 0.15s ease-in-out;
+	-ms-transition: 	opacity 0.15s ease-in-out;
+	-o-transition: 		opacity 0.15s ease-in-out;
+	transition: 		opacity 0.15s ease-in-out;
+}
+.container .message > .info .notification a.home:hover { opacity: <%= opacity %>; }
+.container .message > .info .notification a.home img { height: 12px; }
+
+/* Footer */
+footer {
+	display: block;
+	position: relative;
+	vertical-align: middle;
+	clear: both;
+	color: #fff;
+	margin:  15px auto 0;
+	padding: 14px 1%;
+	box-sizing: border-box;
+	max-height: <%= footer %>;
+	z-index: 1100;
+}
+
+footer .app  		{ text-transform: uppercase; }
+footer .app strong  { font-size: 1em; letter-spacing: 1px; }
+footer .app span    { font-size: 0.9em; }
+
+footer .connect {
+	display: block;
+	float: right;
+	clear: both;
+	text-align: center;
+}
+
+footer .connect:hover a { opacity: <%= opacity * 0.5 %>; }
+footer .connect a 		{
+	display: inline-block;
+	opacity: <%= opacity * 0.7 %>;
+	padding-left: 4px;
+	margin: 0 -1px; /* Use 0 -1px for inline block & ERB - HAML removes whitespace; ERB does now - http://haml.info/docs/yardoc/file.REFERENCE.html#whitespace_removal__and_ */
+	transition: opacity 0.2s ease;
+}
+
+footer .connect a img 				{ display: block; vertical-align: middle; }
+footer .connect a.facebook img 		{ height: <%= size * 0.85 %>px; }
+footer .connect a.twitter  img		{ height: <%= size * 0.85 %>px; }
+footer .connect a.linkedin img		{ height: <%= size * 0.9 %>px; }
+footer .connect a.youtube  img		{ height: <%= size * 0.875 %>px; }
+footer .connect a.fusion   img		{ height: <%= size %>px; }
+footer .connect:hover a:hover 		{ opacity: 1; }