[5.3] Add mime type to disk storage via UploadedFile

[jodiedunlop]

Although mimetype is a supported configuration option for Flysystem, there is no way to pass this though the FileSystemAdapter put() method and consequently any of the convenience functions in UploadedFile. This commit adds support for a mimeType parameter for all of the store functions within UploadedFile and to the Illuminate\Filesystem\FilesystemAdapter class.

[jodiedunlop]

Store file with image/jpeg mime type:
$uploadedFile->storePublicly('folder', 's3', 'image/jpeg');

Store file with auto mime type (calls getMimeType()) by passing (boolean) true:
$uploadedFile->storePublicly('folder', 's3', true);

[caiquecastro]

I think there is a mistake when passing parameters to storeAs method.

[fernandobandeira]

Following @caiquecastro comment...
There should be a null here before $mimeType, currently you're passing the $mimeType as the $visibility parameter.

[taylorotwell]

I implemented this in Laravel 5.4 by allowing an array of options to be passed to these methods:

Storage::disk('local')->put('something', 'hello world', [
    'visibility' => 'public',
    'mimetype' => 'text/plain'
]);

[martinbean]

@taylorotwell Is this functionality not going to be back-ported to Laravel 5.3 then? As it’s a bit awkward having everything sent to S3 with a MIME type of application/octet-stream.

[GrahamCampbell]

No, 5.4 is only a few weeks away anyway. :)

[martinbean]

@GrahamCampbell But it’s useful for applications now and not every one will be upgrading to 5.4 on launch day.

[captbrogers]

I agree with @martinbean, I had this problem just a few weeks ago. I had to use the AWS SDK directly to allow the mime type to be set while still allowing the file to be streamed instead of uploaded the my server then moved over to S3.

[jrean]

Same issue and headache with 5.3

[ingageco]

Same issue with 5.3 - can't upgrade to 5.4 yet due to lack of support from a few packages.