README.md in logster-0.1.5 vs README.md in logster-0.1.6

@@ -15,22 +15,20 @@
 
 And then execute:
 
     $ bundle
 
-Make Logster available in your development environment by adding the following to your routes.rb:
+Make logster web available add the following to your `routes.rb`:
 
 ```
-if Rails.env == "development"
-  mount Logster::Web => "/logs"
-end
+mount Logster::Web => "/logs", lambda { |req| req.session["admin"] }
 ```
 
-Logster will be available in your Rails app in **development** mode only. To wire up in production you will need to set
+Out of the box, logster will use the default redis connection, to customise, in `config/application.rb`
 
 ```
-Logster.config.authorize_callback = lambda{|env| your_own_can_see_logs? }
+Logster.store = Logster.RedisStore.new(redis_connection)
 ```
 
 ## Usage
 
 The concept is to have an embedded "exception reporting service" admins can view on live sites.
@@ -82,5 +80,10 @@
   - Render hashes provided via Logster.add_to_env
 - 2014-08-05: Version 0.1.3
   - Automatically include ignore filter
 - 2014-08-08: Version 0.1.4
   - Fix crash in ignore filter
+- 2014-08-10: Version 0.1.5
+  - Fix crash in Rails 3
+- 2014-08-13: Version 0.1.6
+  - Simplify install process
+  - Fix crash on 404 in /logs dir