For Urvashi's review: Handle repeated deployments by editing the code that generates deploy.sh closes #126

This should handle repeated deployments.
- Because the shell script is blocking, once the new image has been pulled down, the existing application container is force removed
- On repeated deployments, the "docker run" command for the database container will simply error out because a container with that name has already been used. This means the first DB container will always be the one used.

Considerations:
- This relies on having a consistent name for the container. We can either set it to 'app' across all use cases or use the container name specified by the user. I would recommend using just 'app' to keep it simple.
- There may be a couple second downtime between the removal of the original application container and the instantiation of the new application container

Note:
Minor un-related updates for the lifter ui.