1
0
Fork 0
Go to file
Andrew Tomaka 49926de6f5
Lock node version to match targeted lambda env
Ran across this lock with checking an environment variable for
undefined.  In whatever node version my system has set as default, an
environment variable that is undefined is set to the string undefined
breaking a check.  This should be revisited later, but for now, let's
just lock the node version.
2018-06-13 19:07:02 -04:00
.env.sample Include sample environment file 2018-03-08 11:26:49 -05:00
.gitignore Initial commit 2018-03-08 11:25:10 -05:00
.node-version Lock node version to match targeted lambda env 2018-06-13 19:07:02 -04:00
Makefile Setup serverless-offline 2018-06-13 19:06:05 -04:00
README.md Add README 2018-03-08 11:29:47 -05:00
docker-compose.yml Replace disappeared dynamodb container 2018-06-13 19:06:18 -04:00
dynamodb-connect.js Initial commit 2018-03-08 11:25:10 -05:00
handler.js Initial commit 2018-03-08 11:25:10 -05:00
package.json Setup serverless-offline 2018-06-13 19:06:05 -04:00
serverless.yml Setup serverless-offline 2018-06-13 19:06:05 -04:00
yarn.lock Setup serverless-offline 2018-06-13 19:06:05 -04:00

README.md

lightspeed-watcher

Track areas currently beign crowd source funded from www.golightspeed.com

Development

  • cp .env.sample .env
    • edit .env to have the zones you are interested in
  • docker-compose up -d
  • make setup
  • make test
    • Will insert into DynamoDB

You can use the shell of the local DynamoDB container to view results: http://localhost:8898

Production

  • cp .env .env.production
    • Remove DYNAMODB_ENDPOINT setting
  • make deploy