Recommend please resources where I can learn internal PHP stuff

Recommend please resources where I can learn internal PHP stuff. l mean resources where I can learn how PHP works inside, it's internal mechanism and etc

https://redd.it/1rgyrf4
@r_php

Someone just created PR with fully working generics

It’s really impressive, performance cost is really low and looks promising I need to test it

Here is PR https://github.com/php/php-src/pull/21317

https://redd.it/1rharkk
@r_php

Laravel OCR & Document Data Extractor - A powerful OCR and document parsing engine for Laravel
https://packagist.org/packages/mayaram/laravel-ocr

https://redd.it/1rgvht1
@r_php

Symfony 6.4.34 released
https://symfony.com/blog/symfony-6-4-34-released?utm_medium=feed&utm_source=Symfony%20Blog%20Feed

https://redd.it/1rf73bq
@r_php

SymfonyLive Paris 2026: "L’IA au service des devs : Anatomie d'un assistant de Code Review"
https://symfony.com/blog/symfonylive-paris-2026-l-ia-au-service-des-devs-anatomie-d-un-assistant-de-code-review?utm_medium=feed&utm_source=Symfony%20Blog%20Feed

https://redd.it/1rfds6e
@r_php

Symfony 7.4.6 released
https://symfony.com/blog/symfony-7-4-6-released?utm_medium=feed&utm_source=Symfony%20Blog%20Feed

https://redd.it/1rf73bx
@r_php

I built a full open-source demo store with Laravel Shopper — Livewire 3, Volt, Flux UI, multi-currency checkout

Hey everyone,

I've been working on Laravel Shopper (an open-source e-commerce framework for Laravel) and just released a complete demo store to showcase what it can do.

Live demo: https://demo.laravelshopper.dev

Source code: https://github.com/shopperlabs/demo.laravelshopper.dev

What's in it:

\- Product catalog with attribute filtering

\- Variant selector with real-time stock checking

\- Multi-step checkout (shipping → delivery → payment)

\- Cash on delivery (Stripe coming soon)

\- Zone-based pricing with currency switching

\- Customer accounts with address management

\- Blog with categories

\- Full admin panel at /cpanel (Shopper + Filament 4)

Tech stack: Laravel 12, Livewire 3, Volt, Flux UI (free edition), Tailwind v4, Filament 4

The entire codebase is open source. Happy to answer any questions about the architecture or patterns used.

https://redd.it/1rgp1lg
@r_php

Introducing the 100-million-row challenge in PHP!
https://github.com/tempestphp/100-million-row-challenge

https://redd.it/1re6suq
@r_php

Can I use Laravel 13 yet?

I know it's not officially releasing til next month but at this point that could be anywhere from 3 days to 3 weeks away. I'm wanting to start a new app now.


I'm curious if it's close enough to where it's safe to assume there will be little to no breaking changes from the 13.x branch now til release? That way I could just cut a new project from the 13.x branch now instead of using 12.x and have to go though a full upgrade a few weeks into the new project.



Does anyone have any insight into this?

https://redd.it/1rhlhzo
@r_php

Distributed locking, concurrency control, queues & notifiers

I had planned to get a bit more built before sharing this but after seeing https://www.reddit.com/r/PHP/comments/1rgc6jq/locksmith\_a\_flexible\_concurrency\_locking\_library/ \- I figured why not.

I've been working on a library that combines locking primitives (lock, semaphore) and/or rate limiters to create a Seal

This can be optionally combined with a Queue \- FIFO, Lottery, Priority etc

And optionally with a Notifier (Mercure, Centrifugo etc)

You could use it for something as simple as a global lock on something:

$seal = new SymfonyLockSeal(
new LockFactory(new LockRedisStore($this->redis)),
'global-lock',
);

$airlock = new OpportunisticAirlock($seal);

if ($result->isAdmitted()) {
// do a thing
}

Concurrency and rate limiting on an external API call:

// 50 RPM, 3 Concurrent
$seal = new CompositeSeal(
new SymfonySemaphoreSeal(
new SemaphoreFactory(new SemaphoreRedisStore($this->redis)),
resource: 'external-api',
limit: 3
),
new SymfonyRateLimiterSeal($fiftyPerMinuteLimit->create('external-api'))
);

$airlock = new OpportunisticAirlock($seal);

if ($result->isAdmitted()) {
// call the API
}

All the way to FIFO queues with notifiers.

I've built some real world examples here - https://airlock.clegginabox.co.uk (there's bots on the queues). I'd love any suggestions on other real world use cases - building the library against them has allowed me to work out a bunch of edge cases I wouldn't have been able to otherwise.

So far I've only got support for Symfony's Lock, Semaphore and RateLimiter. I plan to add Laravel's Lock and RateLimiter & framework support for both Symfony and Laravel.

Only Mercure as far as notifiers - what else do people use and would like to see support for?

I also plan to release some web components to make wiring up the front end of a queue much easier.

Would love to hear any thoughts, feedback, suggestions. Cheers!

Examples: http://airlock.clegginabox.co.uk

Code: https://github.com/clegginabox/airlock-php

Docs: https://clegginabox.github.io/airlock-php/

https://redd.it/1rhrqym
@r_php

Started writing Clean Code in Laravel... Four chapters in so far, still early days, but excited to share it here

https://mayahi.net/books/clean-code-in-laravel

https://redd.it/1rhu6hx
@r_php

A Week of Symfony #1000 (February 23 – March 1, 2026)
https://symfony.com/blog/a-week-of-symfony-1000-february-23-march-1-2026?utm_medium=feed&utm_source=Symfony%20Blog%20Feed

https://redd.it/1rhuevu
@r_php

V1.0.3 Release Planned – Looking for suggesstions

We’re preparing for our v1.0.1 release of an open-source LMS project built primarily with PHP, along with HTML, Bootstrap, and some JavaScript.


In planned release, we will launch:

1. Marketplace for publishing plugins, applications, connectors like payment gateways / HRMS, ZOOM , GOOGLE meet etc..

2. Few modules already developed like zoom ,external storage on S3.


However, I am mostly into sprint planning, functionality requirement, GIT issues creation, QA etc.. hence not purely into development , So I need recommendation on the code structure, architecture gaps , best practices etc..


Also contributors welcome to checkout the project.

Repo & open issues:
https://github.com/Tadreeb-LMS



https://redd.it/1rhwf89
@r_php

Do you regularly test restoring production from backups?

Hi everyone! I wanted to ask the community: in your companies, do you practice data recovery from backups as a kind of training exercise? For example, do you run simulations where the production environment goes down and you have to quickly restore your servers and databases from those backups? I’m curious how often this is done and how it works for you.

https://redd.it/1ri1ijf
@r_php

Open sourcing a module-first Laravel SaaS foundation (Stripe billing, Filament admin, SSR, Playwright tests)

Hi everyone,

I've open sourced a project I've been using to structure larger Laravel SaaS applications: **Saucebase**.

The core idea is a **module-first architecture** where features install directly into your application instead of living inside vendor packages, inspired by the copy-and-own philosophy behind shadcn/ui.

When you install a module, the code lands in `/modules` in your repo. It's yours. Each module owns its:

* Routes
* Migrations
* UI (Vue pages + components)
* Config
* Policies
* Tests (PHPUnit + Playwright)
* Business logic

Modules integrate through Laravel service providers and auto-register their routes, migrations, assets, and navigation. The app grows by composition while keeping full code ownership, no vendor lock-in. (using nWidart/laravel-modules)

**Stack**

* Laravel 12 + PHP 8.4
* Vue 3 (Composition API) + Inertia.js 2.0
* TypeScript 5.8
* Tailwind CSS 4
* shadcn-vue components
* Docker (with auto SSL certs)
* SSR support (opt-in per page)

**What's included**

* Auth module (login, register, password reset, email verification, etc)
* Socialite authentication (Google, GitHub)
* Filament 5 admin panel
* Roles & permissions (via Spatie)
* User impersonation with recent history
* Stripe billing (subnoscription flow)
* Modular navigation system (modules register their own nav items)
* PHPStan level 5, Pint, ESLint, commitlint
* PHPUnit + Playwright E2E, pre-configured per module
* One-command setup: `php artisan saucebase:install`

>Create your own ***recipes*** based in existing modules.

**Why not just use a traditional starter kit?**

Most starter kits keep you inside their package. You can't easily customize auth logic, change how billing works, or restructure features without hacking around the package's assumptions. You can still installing vendor packages, but you likely need to integrate manually.

With Saucebase, the first `composer require saucebase/auth` copies the code into your repo and that's it , you're the vendor from day one. If the module has some update, just run `composer update` and merge the changes yourself.

Still in active development, not production-ready yet. Looking for feedback from people building real SaaS products - what would you add, remove, or do differently?

* GitHub: [https://github.com/sauce-base/saucebase](https://github.com/sauce-base/saucebase)
* Demo: [https://demo.saucebase.dev/](https://demo.saucebase.dev/)
* Docs: [https://sauce-base.github.io/docs/](https://sauce-base.github.io/docs/)

https://redd.it/1ri1uc0
@r_php