CORS issue with MinIO

@pSouper I figured it out, Here is my best attempt at explaining what I found and how I got it working.

Livewire creates signed urls for the temp uploads and it seems minio does not support this.

see the warning here: https://laravel.com/docs/9.x/sail#file-storage, and from watching caleb's screencasts (the creator of livewire) it looks like thats how it's done.

In order for this to work you have to store your temp stuff in a local diks.

1. I published my livewire configuration and made sure to set the key 'disk' -> 'local'
2. I went into mino and created a bucket, set the bucket to public
3. Then by reading the documentation https://laravel.com/docs/9.x/sail#file-storage i made sure to set my AWS_URL=http://localhost:9000/local variable. This part got me too, that part on the end of the url the "local" has to match the name of your bucket exactly so if your bucket name is "my_cool_bucket" it should be AWS_URL=http://localhost:9000/my_cool_bucket
4. Make sure your APP_URL env variable is http://localhost/ or http://127.0.0.1 or if you use an actual domain set it to that.

What i understood from all this is that at least for now you cant use livewire to create temp urls using minio so you're gonna have to using local storage for temp files. probly better anyhow.

I have no idea why this got it working but this is the only way it functioned. It could be due to minio not supporting signed temp urls, it could be maybe livewire only listens to it's own config, or it could be that the app url env variable is not set right. idk.... maybe someone smarter than me will come along and figure it out and /or explain whats going on / patch it. By all means please correct me if I'm way off. Best of luck to you future laravel peeps. Peace!

@DM-Miguel many thanks, sorry I hadn't replied sooner.

@DM-Miguel Hi, I hadn't seen your post before I started developing a project using Filament (which uses Livewire behind the scenes) + MiniO

The same problem happened and so far there has been no real solution for it. Who knows, maybe there will be an update on this soon.

@DM-Miguel You are correct on your finding however I believe we can get a result with this.

From my research I have come to the same conclusion as you. After a bit more Googling I also found that Minio server can allow self sign but it require a few extra steps, which basically entails using assign CAs see documentation here

https://min.io/docs/minio/linux/operations/network-encryption.html?ref=docs-redirect#install-certificates-from-third-party-cas

From what I can tell Self-signed, Internal, Private Certificates, and Public CAs with Intermediate Certificates can be done and is explain on the page. I believe with a bit of work we could create a CA for Minio server that would allow Livewire to use the tmp folder just like you can do on AWS or Digital Ocean Spaces thus removing the need to use your local storage.

How exactly this is done, I'm not 100% sure yet, but I'll do a bit of work on it and see if I can find the missing piece.