Fix Dockerfile only and forget about Travis CI

[kaihendry]

https://github.com/unee-t/frontend/pull/750 which I think solves https://github.com/unee-t/frontend/pull/892#issuecomment-583220464 because it locks down to .meteor/release

[kaihendry]

Finally managed to get AWS CodeBuild to appear in the checks:

it's got to the point where I am fed up with Travis & I'd rather use the simpler Dockerfile driven approach of what I originally have here: https://github.com/unee-t/frontend/blob/master/buildspec.yml using CodeBuild @franck-boullier

And it succeeded:

So CodeBuild successfully now builds the Docker image and pushed the image to https://hub.docker.com/repository/registry-1.docker.io/uneet/frontend/tags?page=1

So Travis CI should ideally as before:

• Do the deployment of a tagged build - this has to be checked since a lot of env stuff has changed
• Do the CI npm t tests - not working and I've have spent hours on this

[franck-boullier]

t's got to the point where I am fed up with Travis & I'd rather use the simpler Dockerfile driven approach of what I originally have here: https://github.com/unee-t/frontend/blob/master/buildspec.yml using CodeBuild @franck-boullier

OK sounds like a sensible approach indeed.