cachewerk / bref-laravel-bridge Goto Github PK

Let's focus on PostgreSQL, but why would ANYONE use something else.

PostgreSQL 9.6 upwards supports idle_in_transaction_session_timeout.

SET SESSION idle_in_transaction_session_timeout = '5min';

https://stackoverflow.com/a/41818410

It's fairly straight forward:
https://github.com/laravel/vapor-core/blob/7ea7c0001795768a0fcb43d89524a7ac1cfef533/src/Runtime/Octane/Octane.php#L60-L125

We've merged the Bref v2 work we've been doing in this repository into the official repository. @georgeboot and I will be active maintainers of brefphp/laravel-bridge.

We'll keep this cachewerk/bref-laravel-bridge repository and Composer package as is, but will not further develop it.

For Bref v2 support, please see https://github.com/brefphp/laravel-bridge

When a queued jobs run longer and times out we should:

• Ensure that $job->failed() is called (via #31)
• Close the database connection

• Explain why this package exists and how we use it
• Publish to packagist.com
• Finish up readme

Currently, each SQS event will trigger a new Lambda instance. Should we instead keep something like Vapor's work command running?

Looks like Vapor does a full deployment and sets VAPOR_MAINTENANCE_MODE.

Let's see if we can set an environment variable without a full build, or re-use the last built package.

serverless/serverless#11089

Can we use the GitHub deployments feature (GitHub Actions) to list all deployments?

• Publish static dummy
• Offer generate command that uses the app name, maybe asks some questions.

Yesterday I had the pleasure of using this Laravel bridge for the first time, and the overall experience was very good. I only had a minor issue with the initial setup I got some chmod errors. The issue was regarding the logging which used the default Laravel settings. So I was curious if it could make sense to override the default logging setting to something more compatible with AWS such as stderr. I think this is something that is also done in the Briefs Laravel bridge, or maybe change the default path to /tmp instead of Laravel's default logging path. If you believe it is a good idea, I would like to make a PR.

Bref is doing something similar https://github.com/brefphp/laravel-bridge/blob/master/src/BrefServiceProvider.php#L58

Encrypting secrets in a during artifact building and loading them from a file might be a better approach for scale. Requires PHP 8.1. Hat tip @GrahamCampbell.

https://github.com/GrahamCampbell/Envelope-Encryption

The secrets injector and the storage directories helper, both write to stdout. This however doesn't work in PHP-FTP and results in a crash.

Ideally we attempt to write to stderr, but wrapped in a try/catch block.

• Setup
• Queues
• FS
• Octane

The package is quite opinionated, let's make it configurable.

• Make ServeStaticAssets optional
• Make ServeStaticAssets assets configurable
• Document usage including the need for BREF_BINARY_RESPONSES
• Make Log::shareContext() configurable

Add full serverless.yml example, including GitHub Actions workflow for deployment.