Create "setup" submodule

[Elrond]

The idea is to create a mediagoblin.setup submodule. This should
contain code to get the app running.

Things to move there (as examples):


-  celery\_setup/ -> setup/celery/
-  util.get\_jinja\_loader (and friends?)
-  setup\_beaker, if/when it's coming
-  Maybe code from MediaGoblinApp.**init**()

This issue is to track this idea.

[Elrond]

I was just playing with it. It gives a major headache up front:
"``mkdir setup && touch setup/__init__.py``" and the tests fail
strangely.
The test system thinks, that ``setup`` is a funcion on the
``mediagoblin`` module to set it up for testing.
I have a very **bad** workaround, which I hate.
So I'm looking for suggestions.

[Elrond]

Okay. The current "solution" is to call the thing "init", not
"setup". Well.

Anyway: I have the dev/init branch up, which moves celery and
get\_jinja\_loader into a new mediagoblin.init submodule.

[Christopher Allan Webber]

Merged. Thanks Elrond!

[Will Kahn-Greene]

The original url for this bug was ​http://bugs.foocorp.net/issues/385 .
Relations:
#68: follows