Updated deployment scripts to deploy database when none exists on server

Database deployment is trickier than static file deployment. However,
capistrano allows deployment of the database files to a "shared" folder
on the server which persists across each deployment. Cap tasks then
create symlinks in the current release directory which points to these
shared database files.

- path.php has been updated from using the hackbytes.db name to path.db
- Capfile and bootstrap script have been updated so that import
  functions are defined in bootstrap and can be called from the Capfile
- deployment, comments and build scripts have been updated to use the
  new database configurations defined in the bootstrap script

Things to be aware of:

  - path.db will be recreated on each build. This is because insertions
    are invoked solely on the development end.

  - comments.db will only be created on the development-end if it does
    not already exist.  This is because users can submit comments at any
    time, and recreating it may erase comments that have been submitted
    and subsequently pulled to the development workstation (via
    comments-pull).

  - After deployment, the comments database is copied to the shared
    directory (if a comments database doesn't already exist there) and
    a symlink is created in the current release directory (thus, giving
    the application access to the database).

    Again, if the comments database already exists in the shared
    directory, deployments will NOT override this database with the one
    on the development end.

    After the comments database is in place in the shared directory,
    management must be done through the appropriate rake tasks
    (comments-pull and comments-push). This ensures that all user
    submitted comments are preserved.

Summary of how the comments database is deployed:

  1 - If no comments.db exists on development workstation, create it.
  2 - Post deploy, if no comments.db exists on server, copy the
  development workstation version into the persistent directory.
  3 - All subsequent comments database management will be done via the
  rake tasks "comments-pull" and "comments-push"; from now on
  deployments and builds will not override or recreate the existing
  databases unless these databases are manually deleted.

Signed-off-by: Byron Sanchez <bfs5030@gmail.com>