exception_handler 0.7.5 → 0.8.0.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: ccc92609ab7af5a0f65736e1578aaef57b51a2d7
-  data.tar.gz: 1843d7a57a2551baa486a8579e60594eca2e2d5f
+SHA256:
+  metadata.gz: ba54148f25815a5f2df409c4261ade99ffa4f2f96c4a0ae354149ba539bffac3
+  data.tar.gz: ee20ae2ed6c8be539b8ffb0388da0b2680aaaaf5aa793a0df49fe38e5230ea2e
 SHA512:
-  metadata.gz: 0af19ea19133e86ad15a43f9324ee923ebdce75a7747543bd57f799ca16c8b14f0f24b81ce6ed144c8a6cd78169c2aa5e0b6c8bc5780af801bf1d169acc57fb9
-  data.tar.gz: 0740300edaa518daf6db9e133b75650684bdcaf3b276b84c7e4568b9fd61d5032d8d0c14c5037ceaa72998c58076d059a7970b2a2d8321dbd95c526cb8e4fddd
+  metadata.gz: e5a14eeb3beb2ffab2fe1289acd377423242d980294cf0872e85ba86aeb7165027de92b2057d034a1730ff4e38fb716b38052c81d1502143a658367e1a1ae23c
+  data.tar.gz: '0890e4e17d5bb8c94cefb0dc24adb8d40f7fc49c8c9cb7f4e6904221e61750dd23f886ce1af3141316f5dc14152e8ae6cabc1bd3285a90a6e5c3646d8fa7783d'

data/.coveralls.yml

@@ -0,0 +1 @@
+service_name: travis-ci

data/.gitignore

@@ -1,33 +1,51 @@
-*.gem
-*.rbc
-.bundle
-.config
-.yardoc
-Gemfile.lock
-InstalledFiles
-_yardoc
-coverage
-doc/
-lib/bundler/man
-pkg
-rdoc
-spec/reports
-test/tmp
-test/version_tmp
-tmp
-*.bundle
-*.so
-*.o
-*.a
-mkmf.log
-*.tmp
-
-# http://stackoverflow.com/questions/8865848/comments-in-gitignore
-# https://gist.github.com/danielpcox/4636520
-
-log/*.log
-pkg/
-spec/dummy/db/*.sqlite3
-spec/dummy/log/*.log
-spec/dummy/tmp/
-spec/dummy/.sass-cache  
+*.gem
+*.rbc
+.bundle
+.config
+.yardoc
+Gemfile.lock
+InstalledFiles
+_yardoc
+coverage
+doc/
+lib/bundler/man
+pkg
+rdoc
+spec/reports
+test/tmp
+test/version_tmp
+tmp
+*.bundle
+*.so
+*.o
+*.a
+mkmf.log
+*.tmp
+.rspec_status
+/coverage/
+
+##########################################################
+##########################################################
+
+# http://stackoverflow.com/questions/8865848/comments-in-gitignore
+
+##########################################################
+##########################################################
+
+# Desktop INI (Windows)
+desktop.ini
+
+# Readme Source (PSD's)
+readme/source
+
+# Git BFG
+.git.bfg-report
+.git.bfg-report/2017-06-29/07-53-00
+
+# Specs
+log/*.log
+pkg/
+spec/dummy/db/*.sqlite3
+spec/dummy/log/*.log
+spec/dummy/tmp/
+spec/dummy/.sass-cache

data/.rspec

@@ -1,4 +1,3 @@
---color
---format progress
---require spec_helper
---format documentation
+--format progress
+--color
+--require spec_helper

data/.slugignore

@@ -0,0 +1,7 @@
+# Ignore art files
+# https://devcenter.heroku.com/articles/slug-compiler#ignoring-files-with-slugignore
+*.psd
+*.pdf
+/test
+/spec
+/readme

data/.travis.yml

@@ -1,5 +1,13 @@
-rvm:
- - 2.2.4
- - 2.3.2
- - 2.4.0
- - ruby-head
+language: ruby
+rvm:
+ - 2.2.4
+ - 2.3.7
+ - 2.4.4
+ - 2.5.1
+ - ruby-head
+notifications:
+    - false
+scripts:
+  - bundle exec rspec
+after_script:
+  - bundle exec rake coveralls:push

data/Gemfile

@@ -1,13 +1,16 @@
-source 'https://rubygems.org'
-
-# Specify your gem's dependencies in custom_error_pages.gemspec
-gemspec
-
-###########################################
-
-#For Testing
-group :test do
-	gem 'coveralls', require: false
-end
-
-###########################################
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in custom_error_pages.gemspec
+gemspec
+
+###########################################
+
+#For Testing
+group :test do
+	gem 'coveralls', require: false
+end
+
+# => Required for Windows
+gem 'tzinfo-data' if Gem.win_platform? # => TZInfo For Windows
+
+###########################################

data/README.md

@@ -1,443 +1,643 @@
-![Exception Handler](readme/title.jpg "Exception Handler Logo")
-
-<p align="center">
-  <font size="4"><strong>Custom 404 & 500 production error pages for Rails 4 & 5.</font></strong>
-</p>
-
-<p align="center">
-  <a href="http://badge.fury.io/rb/exception_handler"><img src="https://badge.fury.io/rb/exception_handler.svg" align="absmiddle"></a>
-  <a href="http://rubygems.org/gems/exception_handler"><img src="http://ruby-gem-downloads-badge.herokuapp.com/exception_handler/0.5.1?type=total&color=brightgreen" align="absmiddle" /></a>
-  <a href="https://codeclimate.com/github/richpeck/exception_handler"><img src="https://codeclimate.com/github/richpeck/exception_handler/badges/gpa.svg" align="absmiddle"/></a>
-  <a href="https://gemnasium.com/richpeck/exception_handler"><img src="https://gemnasium.com/richpeck/exception_handler.svg" align="absmiddle"></a>
-  <a href='https://coveralls.io/github/richpeck/exception_handler?branch=master'><img src='https://coveralls.io/repos/github/richpeck/exception_handler/badge.svg?branch=master' alt='Coverage Status' align="absmiddle" /></a>
-  <a href="https://travis-ci.org/richpeck/exception_handler"><img src="https://travis-ci.org/richpeck/exception_handler.svg?branch=master" align="absmiddle"></a>
-</p>
-
-<p align="center">
-  <strong><a href="#install">Install</a></strong> → <strong><a href="#config">Setup</a></strong> → <strong><a href="#support">Support</a></strong>
-</p>
-
----
-
-<p align="center">
-  <img src="readme/version.jpg" /><br/>
-</p>
-
-<p align="center">
-  <img src="readme/check.png" height="22" title="Fully Responsive"               align="absmiddle" />&nbsp; <strong>Responsive</strong> &nbsp;
-  <img src="readme/check.png" height="22" title="Branded Error Pages"            align="absmiddle" />&nbsp; <strong>Branded Error Pages</strong> &nbsp;
-  <img src="readme/check.png" height="22" title="Middleware Exception Handling"  align="absmiddle" />&nbsp; <strong>Middleware Exception Handling</strong> &nbsp;
-  <img src="readme/check.png" height="22" title="Keep Users Informed"            align="absmiddle" />&nbsp; <strong>Fully Customizable</strong> &nbsp;
-</p>
-
-<p align="center">
-  <img src="readme/branded/1.jpg" width="425" title="Fully Branded Error Pages" /> <img src="readme/branded/2.jpg" width="425" title="Fully Branded Error Pages" />
-  <img src="readme/branded/3.jpg" width="425" title="Fully Branded Error Pages" /> <img src="readme/branded/4.jpg" width="425" title="Fully Branded Error Pages" />
-</p>
-
----
-
-<p align="center">
-  <img src="readme/rails.jpg" title="Version 0.7.5 Released Early 2017" />
-</p>
-
----
-
-<p align="center">
-  <img src="readme/titles/rails5.png" title="Fully Rails 5 Compatible" width="625" />
-</p>
-
-<p align="center">
-  <img src="readme/check_02.png" height="22" title="New Controller"           align="absmiddle" />&nbsp; <strong align="absmiddle">New Controller</strong> &nbsp;
-  <img src="readme/check_02.png" height="22" title="New Middleware"           align="absmiddle" />&nbsp; <strong align="absmiddle">New Middleware</strong> &nbsp;
-  <img src="readme/check_02.png" height="22" title="Full Test Suite"          align="absmiddle" />&nbsp; <strong align="absmiddle">Full Test Suite</strong> &nbsp;
-  <img src="readme/check_02.png" height="22" title="Rails 4 & 5 Compatible"   align="absmiddle" />&nbsp; <strong align="absmiddle">Fully Rails 4 & 5 Compatible</strong> &nbsp;
-</p>
-
-Brand new `controller` & `middleware` have made **`ExceptionHandler`** even more powerful & efficient. Now you can use `ExceptionHandler` with a [single click](#install) → **plug and play** custom exception pages:
-
-<p align="center">
-  <br />
-  <img src="readme/400.png" title="400 Errors" width="430" />
-  <img src="readme/500.png" title="500 Errors" width="430" />
-</p>
-
-<p align="center">For over 3 years, <strong>ExceptionHandler</strong> has provided production-level <strong>Rails</strong> exception handling for <strong>4xx</strong> and <strong>5xx</strong> errors:</p>
-
-![HTTP Error Codes][http_codes]
-
-Since **browsers only read `4xx` & `5xx` error codes**, all Rails exceptions have to be inferred. Thus, `ExceptionHandler` simply has to manage how the `4xx` / `5xx` errors are passed to the browser.
-
-Unlike other gems, **`ExceptionHandler` uses a custom [`controller`](app/controllers/exception_handler/exceptions_controller.rb) to build an [`@exception`](app/models/exception_handler/exception.rb) object**. This allows us to save the exception, email it or do anything else we may need. The gem has already been a massive success and we continue to actively maintain it.
-
-Now you can try for yourself ...
-
-
-----
-
-<p align="center">
-  <br />
-  <img src="readme/titles/middleware.png" title="Middleware-Powered Exceptions" width="400" />
-</p>
-
-The secret lies in [**`config.exceptions_app`**][exception_app] ↴
-
-> **`config.exceptions_app`** sets the exceptions application invoked by the **`ShowException`** middleware when an exception happens. Defaults to **`ActionDispatch::PublicExceptions.new(Rails.public_path)`**
-
-![Exceptions handled by the ActiveDispatch::ShowExceptions Middleware][middleware]
-
-Each time an exception is raised, [`ShowExceptions`][show_exception] takes the request and forwards it to `config.exceptions_app`. This is expected to return a response - allowing us to inject a [`controller`](app/controllers/exception_handler/exceptions_controller.rb):
-
-> ```app.config.exceptions_app = ->(env) { ExceptionHandler::ExceptionsController.action(:show).call(env) }```
-
-![config.exceptions_app - The key to all Rails exceptions][exceptions_app]
-
-Because our callback maintains the request, we are able to do whatever we need before serving a response. This is a **major** advantage over the "default" (routes). The routes invokes Rails twice and does not persist the request.
-
- **`ExceptionHandler` is the only gem to provide middleware-powered exception handling.**  It populates our custom `view` with details, giving us the ability to **maintain branding** when exceptions are raised:
-
-![Exceptions handled by the ActiveDispatch::ShowExceptions Middleware][middleware]
-
-**`ExceptionHandler` is the most EFFECTIVE and EFFICIENT gem to handle exceptions in Rails**.
-
-Once invoked, its `model`, `controller` and `views` work together to serve the best responses to Rails errors ...
-
-----------
-
-<p align="center" id="install">
-  <br />
-  <img src="readme/titles/install.png" title="1 Click Install for ExceptionHandler 0.7.0 on Rails 5" width="400" />
-  <br />
-  <strong>Custom Rails Error Pages - ZERO configuration needed:</strong>
-  <br />
-</p>
-
-<p align="center">
-  <a href="http://rubygems.org/gems/exception_handler"><img src="readme/gem.jpg" /></a> <a href="http://rubygems.org/gems/exception_handler"><img src="readme/gemfile.jpg" /></a>
-</p>
-
-
-<p align="center">
-  You can install it from the <strong>CLI</strong> or <strong>Gemfile</strong> - it will AUTOMATICALLY run in <strong>production</strong>.
-  <br />
-  <strong>↓ To run in development, use <a href="#dev-mode">dev mode</a> ↓</strong>
-</p>
-
----
-
-<p align="center">
-  If you want to set it up your way, you can use these features...
-</p>
-
-<p align="center">
-  <a href="#config"><img src="readme/titles/icons/config.png" alt="Cinfiguration Options" align="absmiddle" height="24" /> Config</a>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#dev-mode" title="Dev Mode"><img src="readme/titles/icons/dev.png" alt="Dev" align="absmiddle" height="24" /> Dev</a>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#database"><img src="readme/titles/icons/database.png" alt="Database" align="absmiddle" height="24" />  Database</a>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#email"><img src="readme/titles/icons/email.png" alt="Email" align="absmiddle" height="24" />  Email</a>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#views"><img src="readme/titles/icons/views.png" alt="Views" align="absmiddle" height="24" />  Views</a>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#locales"><img src="readme/titles/icons/locales.png" alt="Locales" align="absmiddle" height="24" />  Locales</a>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#custom-exceptions"><img src="readme/titles/icons/custom.png" alt="Custom Exceptions" align="absmiddle" height="24" />  Custom Exceptions</a>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#generators"><img src="readme/titles/icons/generators.png" alt="Generators" align="absmiddle" height="24" />  Generators</a>
-</p>
-
-----
-
-## Config
-
-**From [`0.4.7`](https://github.com/richpeck/exception_handler/releases/tag/0.4.6), `ExceptionHandler` manages its [config](lib/exception_handler/config.rb#L45) from the central Rails `config` hash:**
-
-[![config][config]](lib/exception_handler/config.rb#L45)
-
-If you're using an [`engine`](http://guides.rubyonrails.org/engines.html), you don't need to use an `initializer`:
-
-    # lib/engine.rb
-    module YourModule
-      class Engine < Rails::Engine
-
-        # => ExceptionHandler
-        # => Works in and out of an initializer
-        config.exception_handler = {
-          dev: false,
-          db:  true
-        }
-      end
-
-    end
-
-You only need to provide the inputs you want, for example:
-
-    # config/application.rb
-    config.exception_handler = { dev: true }
-
-    # config/environments/production.rb
-    config.exception_handler = { social: { fusion: "flutils" }}
-
-----
-
-## Dev Mode
-
-**To enable `ExceptionHandler` in dev, enable the [`dev`](lib/exception_handler/config.rb#L38) option:**
-
-    # config/application.rb
-    config.exception_handler = { dev: true }
-
-![Dev][dev_mode]
-
-This disables [`config.consider_all_requests_local`](http://guides.rubyonrails.org/configuring.html#rails-general-configuration), making Rails behave as it would in production:
-
-![Dev][dev_img]
-
-This should be used temporarily.
-
-----
-
-## Database
-
-**We also have `ActiveRecord` integration.**
-
-If you want to save your exceptions to `db`, you need to enable the `db` config option:
-
-    # config/application.rb
-    config.exception_handler = {
-      db: true
-    }
-
-This enables `ActiveRecord::Base` on the [`Exception`](app/models/exception_handler/exception.rb) class, allowing us to save to the database.
-
-In order for this to work, your db needs the correct table.
-
-To do this, once you've enabled the option, run `rails db:migrate` from your console. Our new [`migration system`](https://github.com/richpeck/exception_handler/tree/readme#migrations) will automatically run the migration.
-
----
-
-## Email
-
-**`ExceptionHandler` also now sends email notifications.**
-
-If you want to receive emails whenever your application raises an error, you can do so by adding your email to the config:
-
-    # config/application.rb
-    config.exception_handler = {
-      email: "your@email.com"
-    }
-
-> **Please Note** this requires [`ActionMailer`](http://guides.rubyonrails.org/action_mailer_basics.html). If you don't have any outbound SMTP server, [`SendGrid`](http://sendgrid.com) is free.
-
-[Full tutorial here](https://github.com/richpeck/exception_handler/wiki/2-Email)
-
----
-
-## Views
-
-**From [`0.7.0`](#070), we overhauled the view system:**
-
-![View][view_img]
-
-[Wiew](app/views/exception_handler/exceptions/show.html.erb) is modular - `@exception` populated with [`locales`](#locales).
-
----
-
-## Locales
-
-**[`0.7.5`](https://github.com/richpeck/exception_handler/releases/tag/0.7.5) introduced [locales](config/locales/exception_handler.yml) ...**
-
-[[ locales ]]
-
-The `ExceptionHandler` view is populated by [`@exception.description`](app/models/exception_handler/exception.rb#L121), which pulls from the `locales`.
-
-If you want custom messages, you need the following. The key is defined by the HTTP [`status_code`](https://github.com/rack/rack/blob/1.5.2/lib/rack/utils.rb#L544)
-
-    # config/locales/en.yml
-    en:
-      exception_handler:
-        not_found: "Your message here"
-        unauthorized: "You need to login to continue"
-        internal_server_error: "This is a test to show the %{status} of the error"
-
-You get access to `%{message}` and `%{status}`, both inferring from `@exception`.
-
----
-
-## Layout
-
-**The `layout` has also been improved ↴**
-
-![Layout][layout_img]
-
-We now assign layouts to the **status code** of the response:
-
-![Layout][layouts_img]
-
-By default, `5xx` errors are shown with our [`exception` layout][layout] - this can be overridden by changing the `config` to use a layout of your choice. If you want to inherit the `ApplicationController` layout, assign the codes to `nil`.
-
----
-
-
-## Custom Exceptions
-
-**Custom Exceptions also supported in [`0.7.5`](https://github.com/richpeck/exception_handler/releases/tag/0.7.5)**
-
-Rails handles this for us - [**`config.action_dispatch.rescue_responses`**][rescue_responses]  ↴
-
-![ActionDispatch][config.action_dispatch.rescue_responses]
-
-You need to add to the `rescue_responses` hash in your app's config (mapped to [`status codes`](https://github.com/rack/rack/blob/1.5.2/lib/rack/utils.rb#L544)):
-
-    # config/application.rb
-    config.action_dispatch.rescue_responses["ActionController::YourError"] = :bad_request
-
-Because `HTTP` can only process `4xx` / `5xx` errors, if `Rails` raises an exception, it needs to assign one of the error status codes. **Default** is [`internal_server_error`](https://github.com/rack/rack/blob/1.5.2/lib/rack/utils.rb#L595) - if you'd prefer your app to just return `500` errors for your custom exception, you don't need to explicitly declare them.
-
----
-
-## Generators
-
-**You can generate `ExceptionHandler` into your own application.**
-
-[[ Generator ]]
-
-The following commands will copy the directories...
-
-    rails g exception_handler:views
-    rails g exception_handler:views -v views
-    rails g exception_handler:views -v controllers
-    rails g exception_handler:views -v models
-    rails g exception_handler:views -v assets
-    rails g exception_handler:views -v views controllers models assets
-
-If you don't include any switches, this will copy **all** the folders put into your app.
-
-Each switch defines which folders you want (EG `-v views` will only copy `views` dir).
-
----
-
-### Migrations (deprecated)
-
-**From [`0.7.5`](https://github.com/richpeck/exception_handler/releases/tag/0.7.5), the `migration` generator has been removed in favour of our own [migration system](lib/exception_handler/engine.rb#L58)**
-
-You don't need to generate a migration any more.
-
-If you set the `db` option in config, run `rails db:migrate` and the migration will be run.
-
-To rollback, use the following:
-
-    rails db:migrate:down VERSION=000000
-
-> The drawback to this is that if you remove `ExceptionHandler` before you rollback the migration, it won't exist anymore. You can **only** fire the `rollback` when you have `ExceptionHandler` installed.
-
----
-
-## Support
-
-[Issues](https://github.com/richpeck/exception_handler/issues)
-
----
-
-## Changelog
-
-### [0.7.5](https://github.com/richpeck/exception_handler/releases/tag/0.7.5)
- - [x] [HTTP status layouts](#layouts)
-
-### [0.7.0](https://github.com/richpeck/exception_handler/releases/tag/0.7.0)
- - [x] Wildcard mime types
- - [x] [Custom exceptions](#custom_exceptions)
- - [x] Test suite integration
- - [x] [Email](#email)
- - [x] [Model backend](#database)
- - [x] Sprockets 4+
- - [x] New layout
- - [x] Readme / wiki overhaul
-
-### [0.6.5](https://github.com/richpeck/exception_handler/releases/tag/0.6.5)
- - [x] Streamlined interface
- - [x] ActiveRecord / Middleware overhaul
- - [x] Supports Sprockets 4+ ([`manifest.js`](http://eileencodes.com/posts/the-sprockets-4-manifest/))
- - [x] Email integration
- - [x] Asset overhaul & improvement
- - [x] Removed dependencies
-
-### [0.5.0](https://github.com/richpeck/exception_handler/releases/tag/0.5.0)
- - [x] Locales
- - [x] Email notifications
- - [x] Full test suite
- - [x] Rails 4.2 & Rails 5.0 native ([`request.env`](https://github.com/rails/rails/commit/05934d24aff62d66fc62621aa38dae6456e276be) fix)
- - [x] Controller fixed
- - [x] `DB` fixed
- - [x] Legacy initializer support ([more](https://github.com/richpeck/exception_handler/wiki/1-Setup))
- - [x] Rails asset management improvement
- - [x] Reduced gem file size
-
-### [0.4.7](https://github.com/richpeck/exception_handler/releases/tag/0.4.6)
- - [x] New config system
- - [x] Fixed controller layout issues
- - [x] Streamlined middleware
- - [x] New layout & interface
-
-----
-
-[![404 + 500 Errors][banner]][rubygems]
-
-<p align="center">
-  <strong><a href="#">ExceptionHandler</a> is now the leading custom error pages gem for Rails.</strong>
-  <br />
-  No other gem is as simple or effective at providing beautiful exception pages in production.
-</p>
-
-<p align="center">
-  <a href="http://badge.fury.io/rb/exception_handler"><img src="https://badge.fury.io/rb/exception_handler.svg" align="absmiddle"></a>
-  <a href="http://rubygems.org/gems/exception_handler"><img src="http://ruby-gem-downloads-badge.herokuapp.com/exception_handler/0.5.1?type=total&color=brightgreen" align="absmiddle" /></a>
-  <a href="https://codeclimate.com/github/richpeck/exception_handler"><img src="https://codeclimate.com/github/richpeck/exception_handler/badges/gpa.svg" align="absmiddle"/></a>
-  <a href="https://gemnasium.com/richpeck/exception_handler"><img src="https://gemnasium.com/richpeck/exception_handler.svg" align="absmiddle"></a>
-  <a href='https://coveralls.io/github/richpeck/exception_handler?branch=master'><img src='https://coveralls.io/repos/github/richpeck/exception_handler/badge.svg?branch=master' alt='Coverage Status' align="absmiddle" /></a>
-  <a href="https://travis-ci.org/richpeck/exception_handler"><img src="https://travis-ci.org/richpeck/exception_handler.svg?branch=master" align="absmiddle"></a>
-</p>
-
-<p align="center">
-  <strong><a href="https://rubygems.org/gems/exception_handler">Download Here</a></strong>
-</p>
-
-----------
-
-:copyright: <a href="http://www.frontlineutilities.co.uk" align="absmiddle" ><img src="readme/fl.jpg" height="22" align="absmiddle" /></a> <a href="http://stackoverflow.com/users/1143732/richard-peck?tab=profile" align="absmiddle" ><img src="https://avatars0.githubusercontent.com/u/1104431" height="22" align="absmiddle" /></a>
-
-<!-- ################################### -->
-<!-- ################################### -->
-
-<!-- Refs -->
-<!-- Comments http://stackoverflow.com/a/20885980/1143732 -->
-<!-- Images   https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet#images -->
-
-<!-- Images -->
-[dev_mode]:         readme/dev_mode.jpg
-[dev_img]:          readme/dev.png
-[layouts_img]:      readme/layouts.jpg
-[layout_img]:       readme/layout.png
-[view_img]:         readme/view.jpg
-[http_codes]:       readme/http_codes.png
-[config]:           readme/config.jpg
-[config.action_dispatch.rescue_responses]: readme/config.action_dispatch.rescue_responses.jpg
-[banner]:           readme/banner.jpg
-[gem]:              readme/gem.jpg
-[gemfile]:          readme/gemfile.jpg
-[middleware]:       readme/middleware.jpg
-[exceptions_app]:   readme/exceptions_app.jpg
-[view]:             readme/titles/view.jpg
-[dev]:              readme/titles/dev.jpg
-[db]:               readme/titles/db.png
-[support]:          readme/titles/support.png "Support"
-[changelog]:        readme/titles/changelog.png "Changelog"
-[contribution]:     readme/titles/contributions.png "Contributions"
-[fl]:               readme/fl.jpg "Frontline Utilities LTD"
-[profile]:          https://avatars0.githubusercontent.com/u/1104431 "R Peck"
-
-<!-- Links -->
-[better_errors]: https://github.com/charliesome/better_errors
-[layout]: app/views/layouts/exception.html.erb
-[status_codes]: http://guides.rubyonrails.org/layouts_and_rendering.html#the-status-option
-[stackoverflow]: http://stackoverflow.com/questions/ask?tags=ruby-on-rails+exception-handler
-[rescue_responses]: http://guides.rubyonrails.org/configuring.html#configuring-action-dispatch
-[latest]: https://github.com/richpeck/exception_handler/releases/latest
-[show_exception]: https://github.com/rails/rails/blob/4-0-stable/actionpack/lib/action_dispatch/middleware/show_exceptions.rb
-[exception_app]: http://guides.rubyonrails.org/configuring.html#rails-general-configuration
-[rubygems]: http://rubygems.org/gems/exception_handler
-[frontlineutilities.co.uk]: http://www.frontlineutilities.co.uk
-[stackoverflow.com]: http://stackoverflow.com/users/1143732/richard-peck?tab=profile
-[fork]: #fork-destination-box
-[pull]:  http://github.com/richpeck/exception_handler/pulls
-[issues]: http://github.com/richpeck/exception_handler/issues
-
-<!-- ################################### -->
-<!-- ################################### -->
+![Exception Handler](readme/title.jpg "Exception Handler Logo")
+
+<!-- Intro -->
+<div id="intro">
+  <h4 align="center"><code><strong><a href="https://www.github.com/richpeck/exception_handler">ExceptionHandler</a></strong></code> is presently the MOST POPULAR exceptions gem for <a href="https://medium.com/ruby-on-rails-web-application-development/custom-400-500-error-pages-in-ruby-on-rails-exception-handler-3a04975e4677">CUSTOM Rails error pages</a>.</h4>
+  <p align="center">
+    With <strong>290,000+ downloads</strong>, it is the *only* gem to provide <strong>custom 400/500 exception pages for Rails 5 & 6</strong>
+  </p>
+  <p><img src="./readme/dev.png" /></p>
+  <h4 align="center">Current <a href="https://github.com/richpeck/exception_handler/releases"><u>0.8.0.0</u></a> (August 2018)</h4>
+</div>
+
+<!-- Badges -->
+<p align="center">
+  <a href="http://badge.fury.io/rb/exception_handler"><img src="https://badge.fury.io/rb/exception_handler.svg" align="absmiddle"></a>
+  <a href="http://rubygems.org/gems/exception_handler"><img src="http://ruby-gem-downloads-badge.herokuapp.com/exception_handler/0.5.1?type=total&color=brightgreen" align="absmiddle" /></a>
+  <a href="https://codeclimate.com/github/richpeck/exception_handler"><img src="https://codeclimate.com/github/richpeck/exception_handler/badges/gpa.svg" align="absmiddle"/></a>
+  <a href='https://coveralls.io/github/richpeck/exception_handler?branch=master'><img src='https://coveralls.io/repos/github/richpeck/exception_handler/badge.svg?branch=master' alt='Coverage Status' align="absmiddle" /></a>
+  <a href="https://travis-ci.org/richpeck/exception_handler"><img src="https://travis-ci.org/richpeck/exception_handler.svg?branch=master" align="absmiddle"></a>
+</p>
+
+<!-- Navigation -->
+<div id="navigation">
+  <p align="center"><img src="https://cdn-images-1.medium.com/max/800/1*CKyKxRXLovcrUOB-s8_jCw.png" width="100%" /></p>
+  <p align="center">
+    <strong>
+      📝 <a href="#introduction">Introduction</a> -
+      ⚠️ <a href="#installation">Installation</a> -
+      🔧 <a href="#configuration">Configuration</a> -
+      ☎️ <a href="#support">Support</a> -
+      ⭐ <a href="#changelog">Changelog</a>
+    </strong>
+  </p>
+  <p align="center"><img src="https://cdn-images-1.medium.com/max/800/1*CKyKxRXLovcrUOB-s8_jCw.png" width="100%" /></p>
+</div>
+
+<!-- Introduction -->
+<div id="introduction">
+  <h4>📝 Introduction</h4>
+</div>
+
+---
+<div>
+  <p><b><code>ExceptionHandler</b></code> replaces Rails' default error pages with <strong>dynamic views</strong>.</p>
+  <p>It does this by injecting <a href="https://guides.rubyonrails.org/configuring.html#rails-general-configuration"><code>config.exceptions_app</code></a> with our controller - allowing us to populate erroneous responses with our own HTML. To understand how this works, you need to appreciate how Rails handles errors:</p>
+  <p align="center"><a href="https://github.com/rails/rails/blob/master/actionpack/lib/action_dispatch/middleware/show_exceptions.rb#L44"><img src="readme/show_exceptions.png" width="550"></a></p>
+  <p>Rails uses <a href="https://github.com/rails/rails/blob/master/actionpack/lib/action_dispatch/middleware/show_exceptions.rb"><code><strong>ActionDispatch::ShowExceptions</strong></code></a> (above) to generate error responses.</p>
+  <p>Because web browsers (Rails is a web framework) can only interpret <a href="https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Response_message">HTTP responses</a>, Ruby/Rails exceptions have to be translated into something a browser can read. This is done by calling the above middleware.</p>
+  <p>--</p>
+  <p>As highlighted, an HTTP response is built independent of the Rails stack. This includes assigning an HTTP status code and HTML response body. It's the response body which <code><strong>ExceptionHandler</strong></code> is designed to override.</p>
+</div>
+
+<!-- Sep -->
+<p align="center">
+  <img src="https://cdn-images-1.medium.com/max/800/1*CKyKxRXLovcrUOB-s8_jCw.png" width="100%" />
+</p>
+
+<!-- Installation -->
+<div id="installation">
+  <h4>⚠️ Installation</h4>
+</div>
+
+---
+
+<div>
+  <p>
+    💎 <u><a href="https://rubygems.org/gems/exception_handler">RubyGems</a></u> (Code) |
+    💻 <u><a href="https://medium.com/ruby-on-rails-web-application-development/custom-400-500-error-pages-in-ruby-on-rails-exception-handler-3a04975e4677">Medium</a></u> (Tutorial)
+  </p>
+  <pre><code># Gemfile
+gem 'exception_handler', '~> 0.8.0.0'</code></pre>
+  <p>Because <b>ExceptionHandler</b> is built around a Rails engine, there is <b>nothing</b> to be done to get it working in production. Installing the Gem <b><i>should</i></b> translate your production 4xx/5xx error pages into dynamic views.</p>
+  <p>Environments <u>other</u> than production (development/staging) required the <a href="#dev"><code>dev</code></a> variable to be <code>true</code>.</p>
+</div>
+
+<!-- Sep -->
+<p align="center">
+  <img src="https://cdn-images-1.medium.com/max/800/1*CKyKxRXLovcrUOB-s8_jCw.png" width="100%" />
+</p>
+
+<!-- configuration -->
+<div id="configuration">
+  <h4>🔧 Configuration</h4>
+</div>
+
+---
+
+<p align="center">
+   <g-emoji class="g-emoji" alias="file_folder" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4c1.png">📁</g-emoji> <a href="#config">Config</a>&nbsp;&nbsp;&nbsp;&nbsp;<g-emoji class="g-emoji" alias="computer" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4bb.png">💻</g-emoji> <a href="#dev" title="Dev Mode">Dev</a>&nbsp;&nbsp;&nbsp;&nbsp;<g-emoji class="g-emoji" alias="floppy_disk" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4be.png">💾</g-emoji> <a href="#db">Database</a>&nbsp;&nbsp;&nbsp;&nbsp;<g-emoji class="g-emoji" alias="email" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/2709.png">✉️</g-emoji>   <a href="#email">Email</a>&nbsp;&nbsp;&nbsp;&nbsp;<g-emoji class="g-emoji" alias="eyeglasses" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f453.png">👓</g-emoji> <a href="#views">Views</a>&nbsp;&nbsp;&nbsp;&nbsp;<g-emoji class="g-emoji" alias="speech_balloon" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4ac.png">💬</g-emoji> <a href="#locales">Locales</a>&nbsp;&nbsp;&nbsp;&nbsp;<g-emoji class="g-emoji" alias="clipboard" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4cb.png">📋</g-emoji> <a href="#layouts">Layouts</a>&nbsp;&nbsp;&nbsp;&nbsp;<g-emoji class="g-emoji" alias="no_entry" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/26d4.png">⛔️</g-emoji> <a href="#custom-exceptions">Custom Exceptions</a>
+</p>
+
+---
+
+<!-- Config -->
+<a name="config"></a>
+
+The **ONLY** thing you need to manage `ExceptionHandler` is its [`config`](https://github.com/richpeck/exception_handler/blob/master/lib/exception_handler/config.rb) settings.
+
+Whilst the gem **works out of the box** (without any configuration), if you want to manage the [`layouts`](#layouts), [`email`](#email), [`dev`](#dev) or the [`database`](#db), you'll need to set the appropriate values in the config hash.
+
+This is done in `config/application.rb` or `config/environments/[env].rb` ↴
+
+```rb
+# config/application.rb
+
+module YourApp
+  class Application < Rails::Application
+
+    # => This is an example of ALL available config options
+    # => You're able to see exactly how it works here:
+    # => https://github.com/richpeck/exception_handler/blob/master/lib/exception_handler/config.rb
+
+    # => Config hash (no initializer required)
+    config.exception_handler = {
+      dev:        nil, # allows you to turn ExceptionHandler "on" in development
+      db:         nil, # allocates a "table name" into which exceptions are saved (defaults to nil)
+      email:      nil, # sends exception emails to a listed email (string // "you@email.com")
+
+      # Custom Exceptions
+      custom_exceptions: {
+        #'ActionController::RoutingError' => :not_found # => example
+      },
+
+      # On default 5xx error page, social media links included
+      social: {        
+        facebook: nil, # Facebook page name   
+        twitter:  nil, # Twitter handle  
+        youtube:  nil, # Youtube channel name / ID
+        linkedin: nil, # LinkedIn name
+        fusion:   nil  # FL Fusion handle
+      },  
+
+      # This is an entirely NEW structure for the "layouts" area
+      # You're able to define layouts, notifications etc ↴
+
+      # All keys interpolated as strings, so you can use symbols, strings or integers where necessary
+      exceptions: {
+
+        :all => {
+          layout: "exception", # define layout
+          notification: true, # (false by default)
+          deliver: #something here to control the type of response
+        },
+        :4xx => {
+          layout: nil, # define layout
+          notification: true, # (false by default)
+          deliver: #something here to control the type of response    
+        },    
+        :5xx => {
+          layout: "exception", # define layout
+          notification: true, # (false by default)
+          deliver: #something here to control the type of response    
+        },
+        500 => {
+          layout: "exception", # define layout
+          notification: true, # (false by default)
+          deliver: #something here to control the type of response    
+        },
+
+        # This is the old structure
+        # Still works but will be deprecated in future versions
+
+        501 => "exception",
+        502 => "exception",
+        503 => "exception",
+        504 => "exception",
+        505 => "exception",
+        507 => "exception",
+        510 => "exception"
+
+      }
+    }
+  end
+end
+```  
+
+For a full retinue of the available options, you'll be best looking at the [`config`](https://github.com/richpeck/exception_handler/blob/master/lib/exception_handler/config.rb) file itself.
+
+--
+
+If using an [`engine`](http://guides.rubyonrails.org/engines.html), you **DON'T need an `initializer`**:
+```rb
+# lib/engine.rb
+module YourModule
+  class Engine < Rails::Engine
+
+    # => ExceptionHandler
+    # => Works in and out of an initializer
+    config.exception_handler = {
+      dev: nil, # => this will not load the gem in development
+      db:  true # => this will use the :errors table to store exceptions
+    }
+  end
+end
+```
+
+The best thing about using a `config` options block is that you are able to only define the options that you require.
+
+If you have particular options you *only* wish to run in `staging`, or have single options for `production` etc, this setup gives you the ability to manage it properly...
+
+---
+
+<!-- Dev -->
+<div id="dev">
+  <h5>💻 Dev</h5>
+</div>
+
+As explained, `ExceptionHandler` does *not* work in `development` by default.
+
+This is because it overrides the `exceptions_app` middleware hook - which is *only* invoked in `production` or `staging`.
+
+<p align="center">
+  <img src="./readme/dev.png" />
+</p>
+
+To get it working in `development`, you need to override the [`config.consider_all_requests_local`](http://guides.rubyonrails.org/configuring.html#rails-general-configuration) setting (a standard component of Rails) - setting it to "false" ↴
+
+<p align="center">
+  <img src="./readme/local_requests.jpg" />
+</p>
+
+This is normally done by changing the setting in your Rails config files. However, to make the process simpler for `ExceptionHandler`- we've added a `dev` option which allows you to override the hook through the context of the gem...
+
+```rb
+# config/application.rb
+config.exception_handler = { dev: true }
+```
+
+This disables [`config.consider_all_requests_local`](http://guides.rubyonrails.org/configuring.html#rails-general-configuration), making Rails behave as it would in production.
+
+Whilst simple, it's not recommended for extended use. Very good for testing new ideas etc.
+
+---
+
+<!-- DB -->
+<div id="db">
+  <h5>💾 DB</h5>
+</div>
+
+To save exceptions to your database, you're able to set the `db` option.
+
+Because we use a `controller` to manage the underlying way the system works, we're able to invoke the likes of a [`model`](https://github.com/richpeck/exception_handler/blob/master/app/models/exception_handler/exception.rb) with other functionality.
+
+Ths is done automatically with the latest version of `ExceptionHandler`.
+
+To do this, once you've populated the option with either `true` or a `string`, run `rails db:migrate` from your console.
+
+Our new [`migration system`](https://github.com/richpeck/exception_handler/tree/readme#migrations) will automatically run the migration.
+
+```rb
+# config/application.rb
+config.exception_handler = { db: true }
+```
+
+This enables `ActiveRecord::Base` on the [`Exception`](app/models/exception_handler/exception.rb) class, allowing us to save to the database.
+
+In order for this to work, your db needs the correct table.
+
+---
+
+<!-- Email -->
+<div id="email">
+  <h5>✉️ Email</h5>
+</div>
+
+`ExceptionHandler` also sends **email notifications**.
+
+If you want to receive emails whenever your application raises an error, you can do so by adding your email to the config:
+
+```rb
+# config/application.rb
+config.exception_handler = {
+  email: "your@email.com"
+}
+```
+
+> **Please Note** this requires [`ActionMailer`](http://guides.rubyonrails.org/action_mailer_basics.html). If you don't have any outbound SMTP server, [`SendGrid`](http://sendgrid.com) is free.
+
+From version [`0.8.0.0`](https://github.com/richpeck/exception_handler/releases/tag/v0.8.0.0), you're able to define whether email notifications are sent on a per-error basis:
+
+```rb
+# config/application.rb
+config.exception_handlder = {
+
+  # This has to be present for any "notification" declarations to work
+  # Defaults to 'false'
+  email: "test@test.com",
+
+  # Each status code in the new "exceptions" block allows us to define whether email notifications are sent
+  exceptions: {
+    :all => { notification: true },
+    :50x => { notification: false },
+    500 =>  { notification: false }
+  }
+}
+```
+---
+
+<!-- Views -->
+<div id="views">
+  <h5>👓 Views</h5>
+</div>
+
+What *most* people want out of the view is to change the way it ***looks***. This can be done without changing the "view" itself.
+
+To better explain, if [`ExceptionsController`](https://github.com/richpeck/exception_handler/blob/master/app/controllers/exception_handler/exceptions_controller.rb) is invoked (by `exceptions_app`), it has **ONE** method ([`show`](https://github.com/richpeck/exception_handler/blob/master/app/controllers/exception_handler/exceptions_controller.rb#L42)).
+
+This method calls the [`show` view](https://github.com/richpeck/exception_handler/blob/master/app/views/exception_handler/exceptions/show.html.erb), which is *entirely* dependent on the locales for content & the layout for the look.
+
+This means that if you wish to change how the view "looks" - you're *either* going to want to change your [layout][layouts] or the [*locales*](#locales). There is NO reason to change the `show` view itself - it's succinct and entirely modular. Whilst you're definitely at liberty to change it, you'll just be making the issue more complicated than it needs to be.
+
+--
+
+We've also included a number of routes which shows in [`dev`](dev) mode (allowing you to test):
+
+<p align="center">
+  <img src="./readme/routes.jpg" />
+</p>
+
+---
+
+<!-- Locales -->
+<div id="locales">
+  <h5>💬 Locales</h5>
+</div>
+
+[Locales](https://github.com/richpeck/exception_handler/blob/Readme/config/locales/exception_handler.en.yml) are used to create interchangeable text (translations/internationalization).
+
+--
+
+In `ExceptionHandler`, it provides the wording for each type of error code.
+
+By default, the English name of the error is used (`"404"` will appear as `"Not Found"`) - if you want to create custom messages, you're able to do so by referencing the error's ["status_code"](https://github.com/rack/rack/blob/master/lib/rack/utils.rb#L492) within your locales file:
+
+```yml
+# config/locales/en.yml
+en:
+  exception_handler:
+    not_found:              "Your message here" # -> 404 page
+    unauthorized:           "You need to login to continue"
+    internal_server_error:  "This is a test to show the %{status} of the error"
+```
+
+You get access to [`%{message}` and `%{status}`](https://github.com/richpeck/exception_handler/blob/master/app/views/exception_handler/exceptions/show.html.erb#L1), both inferring from an [`@exception`](https://github.com/richpeck/exception_handler/blob/master/app/controllers/exception_handler/exceptions_controller.rb#L20) object we invoke in the controller...
+
+ - `%{message}` is the error's actual message ("XYZ file could not be shown")
+ - `%{status}` is the error's status code ("Internal Server Error")
+
+--
+
+By default, only `internal_server_error` is customized by the gem:
+
+```yml
+# config/locales/en.yml
+en:
+  exception_handler:
+    internal_server_error: "<strong>%{status} Error</strong> %{message}"
+```
+---
+
+<!-- Layouts -->
+<div id="layouts">
+  <h5>📋 Layouts</h5>
+</div>
+
+The most attractive feature of `ExceptionHandler` (for most) is its ability to manage [`layouts`](https://guides.rubyonrails.org/layouts_and_rendering.html#structuring-layouts) for HTTP status.
+
+--
+
+The reason for this is due to the way in which Rails works → the "layout" is a "wrapper" for the returned HTML (the "styling" of a page). If you have no layout, it will render the "view" HTML and nothing else.
+
+This means if you want to change the "look" of a Rails action, you simply have to be able to change the `layout`. You should not change the view at all.
+
+To this end, `ExceptionHandler` has been designed around providing a [SINGLE VIEW](app/controllers/exception_handler/exceptions_controller.rb#L44) for exceptions. This view does not need to change (although you're welcome to use a [`generator`][generators] to do so) - the key is the `layout` that's assigned...
+
+- [`4xx`](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#4xx_Client_errors) errors are given a `nil` layout (by default) (inherits from `ApplicationController` in your main app)
+- [`5xx`](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#5xx_Server_errors) errors are assigned our own [`exception`](app/views/layouts/exception.html.erb) layout:
+
+```rb
+# config/application.rb
+config.exception_handler = {
+
+  # The new syntax allows us to assign different values to each HTTP status code
+  # At the moment, only 'layout' & 'notification' are supported
+  # We plan to include several more in the future...
+
+  exceptions: {
+    all: { layout: nil } # -> this will inherit from ApplicationController's layout
+  }
+}
+```
+
+The `layout` system has changed between [`0.7.7.0`](releases/tag/v0.7.7.0) and [`0.8.0.0`](releases/tag/v0.8.0.0).
+
+Building on the former's adoption of HTTP status-centric layouts, it is now the case that we have the `all`, `5xx` and `4xx` options - allowing us to manage the layouts for blocks of HTTP errors respectively:
+
+```rb
+# config/application.rb
+config.exception_handler = {
+
+  # Old (still works)
+  # No "all" / "4xx"/"5xx" options
+  layouts: {
+    500 => 'exception',
+    501 => 'exception'
+  },
+
+  # New
+  exceptions: {
+    :all => { layout: 'exception' },
+    :4xx => { layout: 'exception' },
+    :5xx => { layout: 'exception' }, # -> this overrides the :all declaration
+    500  => { layout: nil } # -> this overrides the 5xx declaration
+  }
+}
+```
+
+We've bundled the [`exception`](app/views/layouts/exception.html.erb) layout for `5xx` errors because since these denote internal server errors, it's best to isolate the view system as much as possible. Whilst you're at liberty to change it, we've found it sufficient for most use-cases.
+
+---
+
+<!-- Custom Exceptions -->
+<div id="custom-exceptions">
+  <h5>⛔️ Custom Exceptions</h5>
+</div>
+
+As mentioned, Rails' primary role is to convert Ruby exceptions into HTTP errors.
+
+Part of this process involves mapping Ruby/Rails exceptions to the equivalent HTTP status code.
+
+This is done with [`config.action_dispatch.rescue_responses`](https://github.com/rack/rack/blob/master/lib/rack/utils.rb#L492).
+
+<p align="center">
+  <img src="./readme/custom_exceptions.png" />
+</p>
+
+Whilst this works well, it may be the case that you want to map your own classes to an HTTP status code (default is `Internal Server Error`).
+
+If you wanted to keep this functionality inside `ExceptionHandler`, you're able to do it as follows:
+
+```rb
+# config/application.rb
+config.exception_handler = {
+  custom_exceptions: {
+    'CustomClass::Exception' => :not_found
+  }
+}
+```
+
+Alternatively, you're able to still do it with the default Rails behaviour:
+
+```rb
+# config/application.rb
+config.action_dispatch.rescue_responses = { 'CustomClass::Exception' => :not_found }
+```
+---
+
+<!-- Generators -->
+<div id="generators">
+  <h5>💼 Generators</h5>
+</div>
+
+If you want to edit the `controller`, `views`, `model` or `assets`, you're able to invoke them in your own application.
+
+This is done - as with other gems - with a single [`generator`](https://github.com/richpeck/exception_handler/blob/master/lib/generators/exception_handler/views_generator.rb) which takes a series of arguments:
+
+    rails g exception_handler:views
+    rails g exception_handler:views -v views
+    rails g exception_handler:views -v controllers
+    rails g exception_handler:views -v models
+    rails g exception_handler:views -v assets
+    rails g exception_handler:views -v views controllers models assets
+
+If you don't include any switches, this will copy **all** `ExceptionHandler`'s folders put into your app.
+
+Each switch defines which folders you want (EG `-v views` will only copy `views` dir).
+
+---
+
+<!-- Migrations -->
+<div id="migrations">
+  <h5>✔️ Migrations</h5>
+</div>
+
+You **DON'T** need to generate a migration anymore.
+
+From [`0.7.5`](https://github.com/richpeck/exception_handler/releases/tag/0.7.5), the `migration` generator has been removed in favour of our own [migration system](lib/exception_handler/engine.rb#L58).
+
+The reason we did this was so not to pollute your migrations folder with a worthless file. Our migration doesn't need to be changed - we only have to get it into the database and the gem takes care of the rest...
+
+> If you set the [`db`][db] option in config, run `rails db:migrate` and the migration will be run.
+
+To rollback, use the following:
+
+    rails db:migrate:down VERSION=000000
+
+The drawback to this is that if you remove `ExceptionHandler` before you rollback the migration, it won't exist anymore.
+
+You can **only** fire the `rollback` when you have `ExceptionHandler` installed.
+
+<!-- Sep -->
+<p align="center">
+  <img src="https://cdn-images-1.medium.com/max/800/1*CKyKxRXLovcrUOB-s8_jCw.png" width="100%" />
+</p>
+
+<!-- Support-->
+<div id="support">
+  <h4>☎️ Support</h4>
+</div>
+
+---
+
+<div>
+  <p>You're welcome to contact me directly at <u><a href="mailto:rpeck@frontlineutilities.co.uk"></a><a href="mailto:rpeck@frontlineutilities.co.uk" ref="nofollow">rpeck@frontlineutilities.co.uk</a></u>.</p>
+  <p>Alternatively, you may wish to post on our <u><a href="https://github.com/richpeck/exception_handler/issues">GitHub Issues</a></u>, or <u><a href="https://stackoverflow.com/questions/tagged/ruby-on-rails+exceptionhandler" rel="nofollow">StackOverflow</a></u>.</p>
+  <p>--</p>
+  <p><a href="https://medium.com/ruby-on-rails-web-application-development/custom-400-500-error-pages-in-ruby-on-rails-exception-handler-3a04975e4677" rel="nofollow"><img src="readme/medium.png" target="_blank" alt="Medium" style="max-width:100%;"></a></p>
+</div>
+
+<!-- Sep -->
+<p align="center">
+  <img src="https://cdn-images-1.medium.com/max/800/1*CKyKxRXLovcrUOB-s8_jCw.png" width="100%" />
+</p>
+
+<!-- Changelog -->
+<div id="changelog">
+  <h4>⭐ Changelog</h4>
+</div>
+
+---
+
+[**1.0.0.0**](https://github.com/richpeck/exception_handler/releases/tag/v1.0.0.0)
+  - [ ] TBA
+
+[**0.8.0.0**](https://github.com/richpeck/exception_handler/releases/tag/v0.8.0.0)
+ - [x] [README](https://github.com/richpeck/exception_handler/issues/52) (focus on utility)
+ - [x] Introduction of `4xx`,`5xx`,`:all` for layouts config
+ - [x] Changed `layouts` to `exceptions` in config    
+ - [x] Email improvement
+ - [x] Streamlined migration
+ - [x] Updated model
+
+[**0.7.7.0**](https://github.com/richpeck/exception_handler/releases/tag/v0.7.7.0)
+ - [x] [HTTP status layouts](#layouts)
+
+**0.7.0.0**
+ - [x] Wildcard mime types
+ - [x] [Custom exceptions](#custom_exceptions)
+ - [x] Test suite integration
+ - [x] [Model backend](#database)
+ - [x] Sprockets 4+
+ - [x] New layout
+ - [x] Readme / wiki overhaul
+
+**0.6.5.0**
+ - [x] Streamlined interface
+ - [x] ActiveRecord / Middleware overhaul
+ - [x] Supports Sprockets 4+ ([`manifest.js`](http://eileencodes.com/posts/the-sprockets-4-manifest/))
+ - [x] Email integration
+ - [x] Asset overhaul & improvement
+ - [x] Removed dependencies
+
+**0.5.0.0**
+ - [x] Locales
+ - [x] Email notifications
+ - [x] Full test suite
+ - [x] Rails 4.2 & Rails 5.0 native ([`request.env`](https://github.com/rails/rails/commit/05934d24aff62d66fc62621aa38dae6456e276be) fix)
+ - [x] Controller fixed
+ - [x] `DB` fixed
+ - [x] Legacy initializer support ([more](https://github.com/richpeck/exception_handler/wiki/1-Setup))
+ - [x] Rails asset management improvement
+ - [x] Reduced gem file size
+
+**0.4.7.0**
+ - [x] New config system
+ - [x] Fixed controller layout issues
+ - [x] Streamlined middleware
+ - [x] New layout & interface
+
+ <!-- Sep -->
+ <p align="center">
+   <img src="https://cdn-images-1.medium.com/max/800/1*CKyKxRXLovcrUOB-s8_jCw.png" width="100%" />
+ </p>
+
+ [![404 + 500 Errors][banner]][rubygems]
+
+ <p align="center">
+   <strong><a href="https://rubygems.org/gems/exception_handler"><code>ExceptionHandler</code></a> provides custom error pages gem for Rails 5+</strong>
+   <br />
+   No other gem is as simple or effective at providing branded exception pages in production
+ </p>
+
+ <p align="center">
+   <a href="http://badge.fury.io/rb/exception_handler"><img src="https://badge.fury.io/rb/exception_handler.svg" align="absmiddle"></a>
+   <a href="http://rubygems.org/gems/exception_handler"><img src="http://ruby-gem-downloads-badge.herokuapp.com/exception_handler/0.5.1?type=total&color=brightgreen" align="absmiddle" /></a>
+   <a href="https://codeclimate.com/github/richpeck/exception_handler"><img src="https://codeclimate.com/github/richpeck/exception_handler/badges/gpa.svg" align="absmiddle"/></a>
+   <a href='https://coveralls.io/github/richpeck/exception_handler?branch=master'><img src='https://coveralls.io/repos/github/richpeck/exception_handler/badge.svg?branch=master' alt='Coverage Status' align="absmiddle" /></a>
+   <a href="https://travis-ci.org/richpeck/exception_handler"><img src="https://travis-ci.org/richpeck/exception_handler.svg?branch=master" align="absmiddle"></a>
+ </p>
+
+ <p align="center">
+   <strong>➡️ <a href="https://rubygems.org/gems/exception_handler">Download & Info</a> ⬅️</strong>
+ </p>
+
+ <!-- Sep -->
+ <p align="center">
+   <img src="https://cdn-images-1.medium.com/max/800/1*CKyKxRXLovcrUOB-s8_jCw.png" width="100%" />
+ </p>
+
+:copyright: <a href="http://www.fl.co.uk" align="absmiddle" ><img src="readme/fl.jpg" height="22" align="absmiddle" /></a> <a href="http://stackoverflow.com/users/1143732/richard-peck?tab=profile" align="absmiddle" ><img src="https://avatars0.githubusercontent.com/u/1104431" height="22" align="absmiddle" /></a> <a href="https://github.com/joehilton" align="absmiddle" ><img src="https://avatars2.githubusercontent.com/u/5063592?s=460&v=4" height="22" align="absmiddle" /></a> <a href="https://github.com/toymachiner62" align="absmiddle" ><img src="https://avatars3.githubusercontent.com/u/485782" height="22" align="absmiddle" /></a> <a href="https://github.com/andrewclink" align="absmiddle" ><img src="https://avatars0.githubusercontent.com/u/688916" height="22" align="absmiddle" /></a> <a href="https://github.com/Startouf" align="absmiddle" ><img src="https://avatars2.githubusercontent.com/u/7388889" height="22" align="absmiddle" /></a> <a href="https://github.com/Tonkonozhenko" align="absmiddle" ><img src="https://avatars0.githubusercontent.com/u/1307646" height="22" align="absmiddle" /></a> <a href="https://github.com/mabako" align="absmiddle" ><img src="https://avatars3.githubusercontent.com/u/125113" height="22" align="absmiddle" /></a> <a href="https://github.com/frankzhao" align="absmiddle" ><img src="https://avatars3.githubusercontent.com/u/555499" height="22" align="absmiddle" /></a>
+
+
+<!-- ################################### -->
+<!-- ################################### -->
+
+<!-- Refs -->
+<!-- Comments http://stackoverflow.com/a/20885980/1143732 -->
+<!-- Images   https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet#images -->
+
+<!-- Images -->
+[banner]:readme/banner.jpg
+
+<!-- Links -->
+[rubygems]: http://rubygems.org/gems/exception_handler
+
+[10x]: https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#1xx_Informational_responses
+[20x]: https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#2xx_Success
+[30x]: https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#3xx_Redirection
+[40x]: https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#4xx_Client_errors
+[50x]: https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#5xx_Server_errors
+
+<!-- Local Links -->
+[db]: #db
+[email]: #email
+[dev]: #dev
+[layouts]: #layouts
+[locales]: #locales
+[configuration]: #configuration
+[generators]: #generators
+[custom-exceptions]: #custom-exceptions
+
+<!-- ################################### -->
+<!-- ################################### -->