assert that settings.SECRET_KEY is set
upgrade sentry to sentry/raven and simplify logging configuration

Apparently Raven stopped supporting SENTRY_TESTING to allow
catching exceptions in debug mode, so we may as well stop trying.
add requirements.txt
update docs to reference requirements.txt
minor documentation update
minor doc update
move to project subdirectory to conform to Django1.4 default project layout
git placeholders for media, static, staticfiles subdirectories
update manage.py to django1.4, add wsgi.py

Both are modified to not require hardcoding of the project name
settings: make Django Debug Toolbar, Raven optional; remove Sentry

Sentry is now a standalone server and isn't compatible with
Django 1.4, so it's not recommended to run it builtin.
update requirements.txt to django1.4
base settings slight refactoring
don't die if settings.SECRET_KEY isn't set, just warn
add test settings

Use with: python manage.py test --settings=skeletor.settings.test
manage.py, settings/base.py tweaks
update .gitignore for the new paths
add fabfile
fabfile: move test() from update() to setup/deploy

We might want to run update without actually running the tests
use local database file instead of /tmp, but ignore it in git/rsync

This avoid accidential clashes when two dj-skeletor-based projects
are on the same machine, and is cleaner anyways.
update documentation to reflect the recent changes