2 ms·
+1 for pipenv I develop using pipenv and then deploy installing the dependencies directly in the folder. It works for AWS lambda and containers, although lambd
by gchamonlive 7y ago
+1 for pipenv
I develop using pipenv and then deploy installing the dependencies directly in the folder. It works for AWS lambda and containers, although lambda layers are a little more tricky to release:
`pipenv lock -r > requirements.txt`
`pipenv run pip install -r requirements.txt -t .`
- mcintyre1994 7y agoYou might find AWS SAM CLI worth looking at if you're finding that awkward : https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-sam-cli-install.html https://docs.aws.amazon.com/serverless-application-model/lat... I used to have a Makefile to do the install dependencies in directory, test locally, zip the directory up, deploy to AWS jobs - but SAM is a really good replacement for that workflow. It uses docker containers too, and the other big thing it makes trivial if you need it is running an API gateway locally so you can test the Lambda as an HTTP API instead of just hacking events in as standard input/function inputs.