restore old help text printing
tweak some strings in the database part
fab: allow for maintenance apache config

When taking the site down for maintenance, check if the file
<webserver>/<environment>-maintenance.conf exists (so maybe
apache/production-maintenance.conf ).  If it does then link that
file instead of the normal apache config while the site upgrade is
taking place.

If you write your new site config to use a static HTML file as a
maintenance page then you get a nice holding page while the site is
down.  With the correct set up you can reuse the live CSS files.

See 3iesite for an example set up.
fablib: Report site downtime

When doing a deploy, take a timestamp just before taking the site
offline and just after bringing it back online.  At the end of the
process, report how long the site was down for.
Merge branch 'develop' into tasklib_refactor

* develop:
  fablib: Report site downtime
  fab: allow for maintenance apache config
fab: do some work on a copy of the project to reduce downtime

NOTE: STILL NEEDS TESTING.  Committing now so I can untangle branches.
Also still need to handle a few edge cases - see TODO: comments in
fablib.

So the broad order used to be:

- do a little work, including making a copy for rollback inc. db dump
- take down the site
- do VCS update virtualenv, database migrations etc
- bring site back up

now it is

- make a copy of the site as "next"
- in next, do the VCS update and virtual env stuff
- take down the site
- move the current site to rollback and do database dump
- move next to replace the old current site
- do database migrations etc
- bring site back up

Which should mean a lot less site downtime when the virtualenv is being
updated.
add notes for future tests to write
Be more specific when checking for mysqldumps

Check for the project name
add DEVELOPING guide
fix import paths for tasks - lost the dye somewhere
fix test that tests help exit status
Set the correct key for db_details password
Correct test for whether grants should be enabled
tasks.py - catch help argument even if redirected
tasks: Fix processing of -h and -t with --deploydir

Make sure docopt will handle it correctly.  And once it is, ensure that
the help text shows the tasks from localtasks, and that -t will describe
tasks in localtasks
Add our standard celery config
make it so more than one celery could exist on a system

By having `/etc/init.d/celerybeat_<project_name>` (and for celerybeat and
`/etc/default` ).
convert examples to cookiecutter

So we can start a new project more easily.

See http://cookiecutter.readthedocs.org/ for more.
Update wsgi handler to use Django 1.4+ convention
Add more files for django cookiecutter project