discourse_docker VS bref

Did you try to run it in a container?

I miss Systemd inside Docker containers so much. IMO, for an app, "one-process per container" is a huge pain and very messy. I have a massively popular software to back up that claim: https://github.com/discourse/discourse_docker

I use phusion/baseimage-docker[1] right now, love every bit of it. Having the database, web server(nginx) and the java backend all in one place works beautifully.

The only pain point is having to write `runit` scripts for startup and shutdown for each service, hence the wish for Systemd inside containers.

1: https://github.com/phusion/baseimage-docker

Discourse provides an open-source community forum. All Discourse posts are indexed by Google, which helps existing users find answers to common questions, and attracts new users through search. We self-host our Discourse forum at https://pipedream.com/community as a Docker container using the discourse-docker project.

End users love PHP because you copy the files into a folder.

That's certainly how people deployed web apps built by other people a decade ago, but these days isn't it more common to use something like Docker?

Deploying a containerized app should be pretty much the same no matter what language it's written in. And Discourse does have a Docker container (https://github.com/discourse/discourse_docker), so I'm not sure the underlying language explains why it isn't popular.

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.