Automatic deploy of frontend using Travis CI
We were unable to verify that our automatic deploy of the frontend was successful, as we had reached our build quota 7 days before sprint 3 was due.
Our strategy for the automatic deploy was to have Travis deploy the backend, and then run deploy_frontend.sh. Deploying the backend would have authenticated the Travis shell and it would have been able to git push to the Heroku repository, which would have deployed the frontend.
Our use of the git subtree push --prefix project-group-13-frontend/ heroku master command came from the fact that nodeJs apps (like the one we created using VueJS) requires the push to be at the top level of the project, where the package.json file is located.
