OmniPay VS bref

Seems like it’s unrelated to OMNY. Looks like it’s just a gateway for payment https://omnipay.thephpleague.com/. Someone more dev-minded might be able to explain more, but might be worth calling your card company

check out https://omnipay.thephpleague.com/ a very extensive library supporting many multiple popular gateways like Stripe. There are many Laravel examples on github for its use.

> If their site is already Wordpress and they ask you to fix it, then your job is to fix their Wordpress site. Where is the shame and disrespect in that?

None. I just finished up such a contract myself earlier this month. I was speaking of building new sites from scratch.

> I agree about the spammy notifications and PHP code snippets. But sometimes code snippets can save time.

Put code in code files, under version control. Not in the database. Not in a blob field that gets eval()ed and is editable by users. This is sane web dev 101.

> I'd be interested to hear what good replacements there are for Wordpress+WooCommerce?

Drupal 7 + Drupal Commerce was very nice back in the day. I don't know the current state of Commerce under Drupal 9 but it's what I'd start looking at first if someone wanted me to build them a store from the ground up. Magento is still around, though I've heard that its code is incomprehensible. And if you're not afraid to take the thin framework or frameworkless route, the Omnipay library [1] combined with standard CRUD for the products should get you pretty far.

1: https://omnipay.thephpleague.com

I didn't know about this project for payment gateways from the article: https://github.com/thephpleague/omnipay

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.