Convert demo to standard GeoTrellis deployment framework

[tnation14]

Overview

This PR adds a pipeline to build/deploy API Server and Nginx Containers to AWS. Also, add Terraform resources for an AWS ECS Service, using CloudFront as a CDN.

Notable changes

• Update Docker/Compose
• Remove azavea.* Ansible scripts from the repository (they're downloaded with ansible-galaxy at the beginning of every provisioning run)
• Add a dockerized deployment environment
• Add containers to serve static files and run the API server
• Replace webpack-dev-server with nginx as the default way to serve static files in development
• Add Terraform configuration for an AWS ECS service using our terraform-aws-ecs-web-service module
• Add STRTA to necessary for build/deployment pipeline
• Configure TravisCI for deployment

Notes

• The JavaScript for main site is broken, and won't pass tests. Scala also throws compilation errors when compiling the ingest JAR, but not the server one. As a workaround, I've skipped JS tests, and only build the server JAR (which I think is the only one we need anyway).

• I ran into some Scala dependency resolution issues, and added a Sonatype repo to get everything to work. I'm not sure if this is WAI, or if the LocationTech repo needs to be updated.

• Although I wanted to keep using webpack-dev-server running in development, making the frontend work with both dev and production URLs proved to be tricky. I opted towards just using Nginx instead.

• The backend service displays a small weighted Overlay, but I'm unsure if it should be larger than it is. @lossyrob can you confirm that the backend is functioning?

Testing

• see https://pointcloud.geotrellis.io
• See Travis CI output
• in development, provision a VM, and run scripts/server. Nginx should be available at http://localhost:8000.
  • I also hit http://localhost:8000/ping to be sure that nginx is rewriting URLs properly.

Fixes #11

[lossyrob]

Having trouble running this. I ran scripts/setup.sh, and then inside the vm scripts/cibuild.sh and scripts/server.sh. Navigating to localhost:8000 I'm getting:

Am I skipping a step?

[tnation14]

I don't think so; I just rebuilt my VM from scratch and was able to run scripts/setup.sh and scripts/server.sh, then hit localhost:8000. scripts/setup.sh runs scripts/update.sh; did any part of that script fail? It seems like the JavaScript bundle didn't build properly.

[tnation14]

@lossyrob Just wanted to circle back and see if you were able to fix your Dev environment issues. Did you have any success after running scripts/update again?

[lossyrob]

Thanks for looping back - I didn't have a watch on on this repo until today, and so didn't see your comment. The Azavea GeoTrellis team is putting this on their next sprint - and if someone else doesn't pick it up I'll be able to take a look when I get from State of the Map travels next week.

[echeipesh]

Encountered the same error as @lossyrob but after vagrant destroy vagrant up ./scripts/setup.sh and ./scripts/update.sh inside the container I was able to see the index.html but the page is unresponsive and the service is is throwing 500 which I have not investigated yet.

I had to bump the dependencies for geotrellis-pointcloud to newly published branch. I assume you guys must have been doing publish-local from feature branch in order to have 1.1.0-PC-SNAPSHOT artifact available? I also assume the demo was working fine with that so I'm possibly looking at some kind of regression with the update to published geotrellis-pointcloud.

[tnation14]

I was able to see the index.html but the page is unresponsive and the service is is throwing 500 which I have not investigated yet.

I ran into this locally, and it was because the API server was silently failing to start with OOM errors. I had some success by setting JAVA_OPTS="-Xmx512M" in the environment section for pc-api-server in docker-compose.yml . Doing

$ docker-compose run --rm pc-api-server

Will start the API server only, so you can see if that is indeed the issue without seeing any other output from Nginx/webpack.

II had to bump the dependencies for geotrellis-pointcloud to newly published branch. I assume you guys must have been doing publish-local from feature branch in order to have 1.1.0-PC-SNAPSHOT artifact available?

Do you mean did I update the geotrellis-pointcloud version? I didn't, this demo is still using 0.1.0-PC-SNAPSHOT. I just corrected a typo in the JAR name.

[pomadchin]

It is a part of https://github.com/geotrellis/geotrellis-pointcloud-demo/pull/16 now