Ensure that zipped database is built

[braughtg]

The .tar.gz version of the empty and sample databases need to be up to date in the dist folder and committed to the repo for the release action. It is easy to forget to do this. One approach would be to have a git-hook (pre-commit or pre-push?) that ensures that the most up to date database image has been built, is in the dist folder, has been committed and will be pushed.

[braughtg]

An alternative or augmentation to this might be to create a release.bash script that handles the creation of a release. The git-hook above could still apply to pushes to development. Then this script would:

• ensures that development and production are up to date with origin
• ensures the databases are built and committed to the development branch
• ensures that development branch has been pushed to origin
• merges development into production
• pushes production to origin
• updates development and production from origin