user-documentation VS bref

I think there are thousands of other things to apply to PHP, rather than this, but if that's the way to go, well, the worse is nothing. Also just look at what https://docs.hhvm.com/ has and PHP doesn't, or go through LOLPHP.

> Are there any large Hack codebases I can explore?

depends what you mean by 'large' - perhaps https://github.com/hhvm/user-documentation ?

> Does anyone know if FB tracks changes to PHP so Hack is "up to date"?

No, for the most part, Hack no longer considers PHP 'upstream'. Exceptions are things like security fixes to extension functions, if that particular extension function was derived from PHP.

> With Hack's extensive static type checking and even contexts / coeffects

Have you used contexts/coeffects?

My understanding is that it's still yet to be fully rolled out to WWW, and nobody outside FB has yet played around with it. IMO it still has some DX issues (https://github.com/facebook/hhvm/issues/8828) and the examples given in documentation don't actually work in real life (https://github.com/hhvm/user-documentation/issues/1016).

I have just released the first working version of a symfony starter project using bref.sh.

As you can see on the website (https://bref.sh/) there's 13 billion monthly AWS Lambda invocations using Bref (PHP).

I have a PHP application (running on Amazon Linux via Bref on Lambda) which has been signing Apple passbooks no problem. I've trying to do various upgrades which includes moving to AWS Linux 2023 which uses OpenSSL 3.

Your best bet is to post an issue on https://github.com/brefphp/bref

multi threading php isnt a burden. laravel with a supervisor + redis + queues works out-of-the-box. you can even run it on lambda (vapor or bref.sh) with almost no hassle.

To generate resource on AWS, you can use aws-sdk into a lambda. While Node or Python is more widely used, you can use PHP bref.sh and the PHP AWS SDK to achieve the same outcome. You'll want to use serverless framework (https://www.serverless.com) .

If you’re deploying in AWS and depending on your app I’d highly recommend using https://bref.sh/. When we changed it made our deploy pipeline so much simpler and our AWS bill much cheaper. Plus infrastructure as code is so useful (we don’t have dedicated dev ops in a team of about 20). Things like adding GD, upgrading PHP, or even adding a redis server become 1 (or a few) lines of change which you can PR and test on staging just like other code changes.

For Lambda, look into https://bref.sh/. For us, running on Lambda was always way cheaper than everything else. However, if you have massive scale that calculation may not hold up.

There's a lot to unpack here from your question. First off, PHP on Lambda WITHOUT docker is possible. Check out https://bref.sh. It works by providing PHP on Lambda like any other runtime. It also provides a Web Hosting experience for PHP on Lambda for those that want to run PHP-FPM.

Failing that, looks like Bref will be the option in place of Vapor.