AWS Lambda and Filament v3
We were deploying v2 on AWS Lambda and it worked because a lot of the JS and icons were inlined, we upgrade to v3 and it appears that is no longer the case. Bref supports binary response but I'm not sure how that applies to loading assets via Livewire templates.
3 Replies
Don’t really understand the issue. Icons should still be inlined. JS is now static instead of routed through Laravel
Lambda cannot return, well by default, JS and CSS (binary) assets from API Gateway. Bref has a construct (serverless plugin) that allows publishing assets to a CloudFront URL and uploading during deployment: https://bref.sh/docs/use-cases/websites
Right now Filament requires all assets to be relative to the
public directory, but would be nice to configure that to load a remote directory/URL to serve CSS and JS from something like Cloudflare.Bref
Serverless PHP websites – Bref
Learn how to deal with assets and static files to deploy serverless PHP websites.
I think if the current way doesn’t work on some systems we are open for a PR but I guess nobody in the team is using AWS Lambda so we can’t really test or figure out what’s needed