I'm working to update and revise a few documents from existing
resources into our documentation (i.e. docs/).

`http://wiki.mediagoblin.org/HackingHowto <http://wiki.mediagoblin.org/HackingHowto>`_

`https://gitorious.org/mediagoblin/pages/HackingWithVirtualenv <https://gitorious.org/mediagoblin/pages/HackingWithVirtualenv>`_

`http://wiki.mediagoblin.org/Storage <http://wiki.mediagoblin.org/Storage>`_

`http://wiki.mediagoblin.org/Processing <http://wiki.mediagoblin.org/Processing>`_

The goal here is to provide an introduction to hacking on
MediaGoblin that outlines both "how to get all of the necessary
components working," in order to begin hacking on GMG.

As part of this, I want to include sections that answer the
questions, "what/where are the (popular) components that one might
be interested in working on," (i.e. templates, db schema,
configuration files, urlmapping.) and "why are things the way they
are," (drawing from existing design documents.)

As part of issue `#483 </issues/483>`_, we're moving documentation
around between the manual (docs/ in mediagoblin repository) and the
wiki. The manual will hold the site administration documentation.

This bug is to outline what that entails and create bugs to write
the resulting content.

This should get done for 0.1.0.

It would be good to have some documentation on how to run celery
separately, especially because that will be necessary for people
who are running with video support in this release.

Some indications on how to run the server separately here:
`http://wiki.mediagoblin.org/HackingHowto#Running\_the\_server <http://wiki.mediagoblin.org/HackingHowto#Running_the_server>`_

Would be good to do this in a separate chapter/section I think from
the deployment section, probably immediately following it.