Enable message queue by default in development.

The current setting whereby it's disabled by default has led to
confusion.  Given rabbitmq is available and configured on the dev VM it
makes sense for this to be enabled by default.

It remains disabled by default for the tests because the test quite
enables it explicitly for the tests that need it.
Merge pull request #69 from alphagov/change_message_queue_default

Enable message queue by default in development.
Add MongoDB instrumentation to action logging

We can generate more fine-grained instrumentation of MongoDB queries directly
in the request logs by subscribing to the notifications generated by moped (the
connection adapter used by mongoid). For example:

  Completed 200 OK in 3ms (Views: 1.2ms | Mongo: 0.7ms)
Use DB payload key logstasher is looking for

By using the same payload key as ActiveRecord, we get the DB duration into the
logstasher output for free.

Note that this assumes that the application is only running mongoid and not
ActiveRecord as well, otherwise the recorded duration would get clobbered by one
or the other.
Upgrade ruby to 2.1.4

To keep up to date etc.
Merge pull request #71 from alphagov/bump_ruby

Upgrade ruby to 2.1.4
Add integration test for Mongo instrumentation
Merge pull request #70 from alphagov/mongodb-instrumentation

Add MongoDB instrumentation to action logging
Make it clear that the "gone item" behaviour isn't implemented

People (read: me) might read this documentation as being part of
functionality that already exists in the content-store.

Remove that assumption by making it clear that it's the intended
behaviour.
Merge pull request #72 from alphagov/add-not-implemented-note-for-gone-items

Make it clear that the "gone item" behaviour isn't implemented