It would be great if we had a tool that could do something like:

::

    ./bin/gmg environment_tarball mediagoblin.ini tarball_name.tar.gz

That contained something like:

::

    ./mediagoblin_db.json
    ./public_store/ # all public store files kept here
    ./queue_store/ # all queue store files kept here

Over time our database format will change, and it'll be important
to be able to update peoples' existing databases. We need both a
way to specify migrations and to be able to run them.

`http://namlook.github.com/mongokit/migration.html <http://namlook.github.com/mongokit/migration.html>`_
contains some info on this.

As far as where the revision info is stored, maybe that could be
kept in something like

::

    settings_document = db['app_settings']['mediagoblin']
    settings_document['db_revision'] = 'some_identifier'

but I'm not sure. I've been thinking that maybe we'll need to store
some user settings in the database eventually once we get some sort
of admin interface around. Maybe this is the first thing to start
storing.

We need to be able to support translations! This is a multi-step
process:


-  we need to be able to put
   `translations in the templates <http://jinja.pocoo.org/docs/extensions/#i18n-extension>`_
-  we need to be able to put them in normal python code
-  we need to be able to extract translations
-  we need to put translations up somewhere where people can start
   translating them (Transifex?)