New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: how to run in aws lambda #87
Conversation
This is amazing. I think we can make it even easier! Would you mind adding a new entry point for the application inside |
@all-contributors add @tom-fletcher for doc |
I've updated the pull request to add @tom-fletcher! 🎉 |
@fox1t I'll have a look at this tomorrow my time. Vercel is a lot more graceful - with Lamba there is no remote build step (so there will always have to be some handler code manually written), but perhaps the logic can be moved into the library so it looks something like this: import { lambdaHandler } from 'turborepo-remote-cache/lambdaHandler';
export const handler = lambdaHandler; |
Following changes have been made:
While I was there, I also added an additional update to the docs to include information on how to use local environment variables to configure Using these env vars can be useful if you don't want to hard-code your |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
In this PR:
A guide on how to run the
turborepo-remote-cache
server in an AWS Lambda Function.Credit to @cpitt for a starting point on the handler code in #28.
This is dependant on #86 - as this change is required to allow the Lambda's temporary credentials to access the S3 bucket.
Issues reference: