Awesome content! Keep it up! I'm using filament for my admin panel from a different domain. For testing purposes, I've left wildcards in the cors config file. It's worth mentioning im using jetstream which comes with its own middleware. But the sanctum is more towards api endpoints. The issue im having is viewing the images from storage folder when I want to view or edit my previously created record from the subdomain. I can however preview them on my record's image column.
what if even though the allow access origin is set up to * or to the actual URL is defined properly, the CORS policty is still blocking the request, what can we do, besides messing up with httpd.config in apaches server?
Great video! I send you an email yesterday, I was wondering if you received it? It briefly touches on https for a Laravel app behind a reverse proxy as well as verifying an email with Laraval Fortify from a different browser as from where the request was made.
Can you make a video about how to work with sanctum staging server with a domain and using localhost for frontend dev environment How to make the localhost talk to the staging and accept cookies without breaking the real staging frontend
I have a instance in amazon aws but my configuration present problems with CORS, I implemented this way for permissions in my other server but not solution my problem, please help
hey, this video was made using laravel 10. you're probably using laravel 11 where some of the config files are not "published". you can either chose to publish them: laravel.com/docs/11.x/configuration#configuration-publishing Or, if you are setting up an application from scratch, scaffold it using Laravel Breeze: laravel.com/docs/11.x/starter-kits#introduction
