Rodolfo Wilhelmy

Y U NO HAML?  HAML is neat. Less is more.

lol, let's start with an AMA what's your first question? On Wed, Mar 8, 2017 at 11:53 AM Bhargav Kowshik wrote: > Yes @rodowi would be great to have some...

yea it's a good idea to upload a custom Dockerfile, but in the meantime you can pull the official image take a look at https://github.com/tensorflow/tensorflow/blob/8cac382a5425d64f3083cb5adec525baa163e18e/tensorflow/tools/docker/README.md#L6, hope that helps

A first step could be to define the infrastructure required by the project as a [Cloudformation template](https://aws.amazon.com/cloudformation/aws-cloudformation-templates/). This would enable us to have visibility of the current infrastructure deployed, assess...

@tyrasd besides EC2 and S3, is there any other type of AWS resources that this project depends on?

_Another benefit of defining a CloudFormation template is that we get "replicability" of the whole deployment process. I'd be happy to help on this._

We could save lots of resources by serving the tiles from Mapbox infrastructure instead of spinning up a [local tile server](https://github.com/hotosm/osm-analytics-cruncher/blob/24d3c09083b300d22e94f41891892ba8df54c547/server/serve.js#L7). The frontend is using Mapbox as a basemap, but...

If we would remove the requirement for serving tiles, this EC2 instance could be running batch jobs on [spot instances](https://aws.amazon.com/ec2/spot/) once a day saving a lot of money, i.e. this...

@cgiovando yes, def we should work this in parallel This is what I see as next steps for testing this out: - [x] I will add an optional script that...

> but how does this save us any money overall? By uploading tiles directly to the Mapbox API we skip S3, saving those 20 USD (4M \* 0.005 / 1000...