We should talk about what kind of server requirements you'll need for about what size deployment somewhere in the deployment docs.

We don't really know yet and this is probably way down the road, so marking this as low priority for now. But once we start doing deployments, it should become higher in priority!

We need to start testing views to make sure they work right. Right now we should create a "test app" to start testing things in.

Use webtest: http://pythonpaste.org/webtest/

The testing app should be importable from something like:

from mediagoblin.tests.tools import get_test_app test_app, webtest_app = get_test_app()

where the test_app is the MediaGoblinApp instance and webtest_app is a wrapped instance in webtest.

The testapp should do the following things:

• create a new database with the database name 'mediagoblinunittests' or something with the default connection settings, dumping an old database if it exists
• Attach a mediagoblin.app.MediaGoblinApp instance to webtest with that database... see the structure of paste_app_factory to see how to do this
• create a public_store and a queue_store that write to temporary directories. Use tempfile.mkdtemp() to create these directories
• when calling setup_celery_from_config it should make sure the mongodb database that it calls is the mediagoblinunittests database we created.

One note: cache the database connection in a global variable like mediagoblin.tests.tools.DATABASE_CONNECTION and also note whether celery is set up in mediagoblin.tests.tools.CELERY_IS_SET_UP... we should only set up celery once :)

There are a series of things that GNU MediaGoblin will send email for.

This issue is to figure out how to GNU MediaGoblin can send email without an MTA running on the local machine.

Perhaps just log sent email to a log file?