Version 2.0 of this Bref-Laravel bridge will be radically different.
Indeed, we are importing all the code and git history of this alternative bridge by CacheWerk: https://github.com/cachewerk/bref-laravel-bridge This bridge is better maintained and supports Laravel far better.
This pull request will be merged once Bref 2.0 is released: the v2.0 of the Laravel bridge will be released at the same time.
Automatically caches the config (if not already cached) on Lambda cold start
Supports a Maintenance mode
Moves the entire storage directory to /tmp (fixes #8)
Optionally serves basic assets (e.g. favicon.ico and robots.txt) from PHP on Lambda
Automatically fixes the config of AWS credentials to support the AWS_SESSION_TOKEN variable
Automatically sets app.mix_url from app.asset_url
Automatically adds the X-Request-ID header to the log context
And more importantly, it changes how SQS queues are handled (this is the most significant breaking change).
Laravel bridge 1.x adapts Laravel Queues to SQS: the retry strategy and storing of failed messages are handled by SQS via serverless.yml. All SQS features are supported, but only a fraction of Laravel Queues features are supported.
Laravel bridge 2.0 follows the official behavior of Laravel Queues instead. Only a fraction of SQS features are supported, but all features of Laravel Queues are supported (e.g. job retry, delay, rate limiting, storing failed messages…).
The reason for this choice is:
Laravel Queues simply has better features for job/queue management.
Over time, we've seen many Laravel developers confused because most Laravel Queues feature were not working.
Laravel users will be able to port existing projects to Lambda without code changes.
FAQ
What about the v1 of this bridge?
The v1 will still be available on GitHub (we'll create a v1 branch) and Composer. It will continue to work, however we will not maintain it anymore (unless for critical security issues).
The CacheWerk bridge will be deprecated in favor of this bridge. The creators and maintainers of the CacheWerk bridge (@tillkruss & @georgeboot) will join this repository as maintainers. The entire git/code history of https://github.com/cachewerk/bref-laravel-bridge is imported into this bridge as v2.0.
mnapoli
commented
1 year ago
Version 2.0 of this Bref-Laravel bridge will be radically different.
Indeed, we are importing all the code and git history of this alternative bridge by CacheWerk: https://github.com/cachewerk/bref-laravel-bridge This bridge is better maintained and supports Laravel far better.
This pull request will be merged once Bref 2.0 is released: the v2.0 of the Laravel bridge will be released at the same time.
What is this PR?
This PR:
masterbranchmasterRelated docs PR: https://github.com/brefphp/bref/pull/1424
What's new?
What will change with v2.0:
storagedirectory to/tmp(fixes #8)AWS_SESSION_TOKENvariableapp.mix_urlfromapp.asset_urlX-Request-IDheader to the log contextAnd more importantly, it changes how SQS queues are handled (this is the most significant breaking change).
serverless.yml. All SQS features are supported, but only a fraction of Laravel Queues features are supported.The reason for this choice is:
FAQ
What about the v1 of this bridge?
The v1 will still be available on GitHub (we'll create a
v1branch) and Composer. It will continue to work, however we will not maintain it anymore (unless for critical security issues).What about https://github.com/cachewerk/bref-laravel-bridge ?
The CacheWerk bridge will be deprecated in favor of this bridge. The creators and maintainers of the CacheWerk bridge (@tillkruss & @georgeboot) will join this repository as maintainers. The entire git/code history of https://github.com/cachewerk/bref-laravel-bridge is imported into this bridge as v2.0.
TODO