http://www.reviewboard.org/docs/codebase/dev/getting-started/#gettingstarted suggests a sequence of steps that result in the sqlite database being created in the "wrong" directory. If:

$ cd reviewboard
$ python ./contrib/internal/prepare-dev.py

Is issued the database ends up in the reviewboard directory (i.e. reviewboard/reviewboard/reviewboard.db of the git working area).

When the next step in http://www.reviewboard.org/docs/codebase/dev/getting-started/#gettingstarted is ran, reviewboard starts but complains about a missing database (schema) and suggests that, "manage.py syncdb" be ran.

This change updates the template settings file to perform some directory checks I'm not sure if this is good form but it is one of the easiest ways of correcting the problem problematically without needing to update the settings file after it is created.

I added an if sqlite check to make clear the path was needed (only for sqlite).