There are two stages: 1) generate cache & lambda.zip 2) launch lambda.zip in sam local container
Stage 1 needs to be repeated any time the schema or source code changes. Stage 1 happpens whenever the docker-compose constellation is started. It can be forced with the command: docker-compose start makecache
Build the lambda.zip and start the database:
docker-compose up -d
Run the sam local api server:
sam local start-api
Open a new terminal and wait for a few minutes after executing:
curl -i \
-H 'Accept: application/json' \
-H 'Content-Type: application/json' \
-XPOST \
-d '{ "query": "mutation { authenticate (input: { clientMutationId: \"cmId\", email: \"user@test.test\", password: \"password\" }) { jwtToken { role } } }" }' http://localhost:3000/graphql
The SQL files are from the forum example
A utility script from vishnubob/wait-for-it https://raw.githubusercontent.com//master/wait-for-it.sh prevents the makeCache script from running before postgres has fully started up.