Direct Beaker integration

[Christopher Allan Webber]

We should bundle Beaker directly into GNU MediaGoblin. Right now
it's set up as middleware in server.ini, but this isn't ideal for
the following reasons:


-  Beaker is in no way optional middleware. It's absolutely
   essential for launching the application.
-  Things like ./bin/gmg shell don't give you a fully functioning
   application because they just read mediagoblin.ini which doesn't
   contain information on how to set up Beaker, so it is never set up
-  We need to have a paste config in order to launch tests
-  Complicates writing scripts that interface with mediagoblin So
   here's a solution.
-  Create a ['beaker'] section in mediagoblin.ini and
   mediagoblin/config\_spec.ini
-  Add a utility to create the beaker instance based on the
   ['beaker'] section of the config
-  Use that utility in MediaGoblinApp.**init**() and push it into
   mg\_globals

[Christopher Allan Webber]

Now that we've added
`http://bugs.foocorp.net/issues/385 <http://bugs.foocorp.net/issues/385>`_
we should probably put this in mediagoblin/init/ ?

[Christopher Allan Webber]

It turns out that middleware might be the only reasonable way to do
the session. Nonetheless, I tend to think we need to move the
configuration of the session middleware over to mediagoblin.ini
instead of paste.ini... you simply can't access some things via
stuff like ./bin/gmg shell right now the way things are because the
session middleware hasn't been set up. So this will take some
careful thinking and I might actually tackle the caching setup
stuff separate from the session stuff while I think it through.
(The cache stuff doesn't so much need to be set up as a
middleware.)

[Will Kahn-Greene]

The original url for this bug was ​http://bugs.foocorp.net/issues/397 .
Relations:
#212: related, #29: related

[Christopher Allan Webber]

If #507 was implemented, this ticket could be closed.