Replies: 3 comments 5 replies
|
I see this as out of scope for this package. For more full media handling capabilities check out our laravel-medialibrary package. |
0 replies
|
I'm gonna give this a +1 - I'm honestly pretty dumbfounded that there's no way to 'save' to a string/buffer. My use case is that I want to make manipulations to images and immediately push those to cloud storage, seems sub-optimal to save them to disk just read them again and then delete them. Am I missing something? |
2 replies
|
Is it still really impossible to use a cloud storage?? |
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
At this point there is no way to opt out of the default image saving pattern which uses php's
copyfunction. It would be a nice addition to be able to manually save the processed image, for ex:I'm guessing additional issue would be image optimization which is executed after image is saved.
All reactions