When using laravel-vapor, the image will not upload to the compute unit (lambda) before passing to s3.
It will stream the file to s3 (using presign url generated from Laravel), then just passing the path of the uploaded file to move to our target destination.
Reference: https://docs.vapor.build/1.0/resources/storage.html#file-uploads
Is there a way to modify the behaviour of the front end image type to be able to add in the code to stream the file to s3 in front end.
I saw there's a place to mutate the backend logic for image type, where can change to use Storage::copy instead of store.
But in the front end might need to have the ability to overwrite to do that?
If there's anything align to the goal of this package, I'm willing to contribute to the package as well.
Thank you.
When using laravel-vapor, the image will not upload to the compute unit (lambda) before passing to s3. It will stream the file to s3 (using presign url generated from Laravel), then just passing the path of the uploaded file to move to our target destination. Reference:
https://docs.vapor.build/1.0/resources/storage.html#file-uploadsIs there a way to modify the behaviour of the front end image type to be able to add in the code to stream the file to s3 in front end.
I saw there's a place to mutate the backend logic for image type, where can change to use Storage::copy instead of store. But in the front end might need to have the ability to overwrite to do that?
If there's anything align to the goal of this package, I'm willing to contribute to the package as well. Thank you.