Olle Bröms

I think lambda only can handle files up to 6mb. https://docs.aws.amazon.com/lambda/latest/dg/gettingstarted-limits.html 

@duveborg Hello mate ;) Long time no see. I think this repo needs to implement presigned urls to workaround that limitation. https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-presigned-url.html

@duveborg I sit in the same boat as you. My workaround right now is to deploy a small docker container using ec2 and run the server below until any lambda...

I'm not sure if this helps anyone who want to implement this but I think that `TURBO_PREFLIGHT` or `--preflight` would be of good use to do this. https://github.com/vercel/turbo/issues/956 https://github.com/vercel/turbo/pull/1052

I've created another repo that just solves s3 and lambda with presigned urls that allows bigger files. https://github.com/EloB/turborepo-remote-cache-lambda ```bash git clone [email protected]:EloB/turborepo-remote-cache-lambda.git cd turborepo-remote-cache-lambda/ npm --prefix=function install sam build zip...

This seems to be completely broken at the moment. Here is a working reproduction script. ```bash # Create docker compose file cat

Looking at the test again I see that admin_init shouldn't run... So maybe it works as intended.