Your Projections Will Fail — Make Them Resilient
https://medium.com/@dariuszgafka/your-projections-will-fail-make-them-resilient-e996650f56cf

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

Your Projections Will Fail — Make Them Resilient
https://medium.com/@dariuszgafka/your-projections-will-fail-make-them-resilient-e996650f56cf

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

Wonderful world of worktrees (and Laravel)
https://joeymckenzie.tech/blog/wonderful-world-of-worktrees-and-laravel

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

Announcing Plans for a PHP Ecosystem Survey and Report
https://thephp.foundation/blog/2026/04/22/announcing-plans-for-a-php-ecosystem-survey/

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

Laravel Reverb + Nuxt 3: Real-Time Messaging, Full Chat App Tutorial
https://youtu.be/bjcM8E5s8p0

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

BETA laravel-permissions-redis v4.0.0-beta.1 — Redis-backed permissions, looking for feedback

Hi ,

Maintainer of [laravel-permissions-redis\](https://github.com/scabarcas17/laravel-permissions-redis) here. Just cut v4.0.0-beta.1 and I'm looking for people to test before I cut stable.

Quick context on what it is

Spatie's laravel-permission is great and it's what most people should use. This package is for a specific case: when you're doing so many permission checks per request (think: a complex admin panel rendering 200+ ACL-gated widgets, or API gateways authorizing fan-out calls) that the DB roundtrips from Spatie become measurable latency.

All reads go to Redis. The DB is only touched on cache miss (warm) or on write (assign/revoke). Writes invalidate and re-warm via events.

What's new in v4.0*

\- Permission `group` metadata preserved in Redis — previously `PermissionDTO::group` was always null, now it's backed by a Redis hash
\- `Role::hasPermission()` — direct role-level check via SISMEMBER
\- Blade directives accept guard override: `@role('admin', 'api')`
\- Queue-backed warming (`--queue` flag on the warm commands)
\- Multi-user-models — `user_model` config accepts an array (useful for User + Admin separation)
\- UUID/ULID role IDs
\- LRU eviction in the in-memory resolver cache + warm cooldown (protects long-running workers and DB storms)
\- `TransactionFailedException` — Redis EXEC failures are observable instead of silently dropped

Breaking

`PermissionRepositoryInterface` gained 3 methods for permission group metadata. If you only use the package as a consumer (not implementing the interface yourself), no code changes required — just run `php artisan permissions-redis:warm --fresh` after upgrade.

Install the beta

composer require scabarcas/laravel-permissions-redis:\^4.0@beta

Release notes: https://github.com/scabarcas17/laravel-permissions-redis/releases/tag/v4.0.0-beta.1

Honest disclaimers

\- This is beta. Don't deploy to prod yet.
\- If your app does <50 permission checks per request, Spatie is probably simpler and fine.
\- Needs Redis. If you can't run Redis, this is not for you.

Open to feedback on: API ergonomics, the upgrade path, whether the new interface methods feel natural, anything else. Will roll feedback into beta.2 or rc.1.

Thanks!

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

PHP will get an AOT compiler from the Swoole team in 2027

>Swoole Compiler v4 introduces a native AOT (Ahead-of-Time) compiler that radically changes the landscape. The AOT compiler abandons traditional PHP interpretation and allows code to be compiled directly into native binary executables. Performance can increase by orders of magnitude compared to the classic interpreter, reaching levels comparable to Rust and Go.

News has appeared in the Chinese segment that Swoole Compiler 4 plans to release a real PHP AOT compiler, roughly 95% compatible with PHP. Some natural limitations like $$, eval, and extract are understandable.

We have effectively already entered the era of AOT compilation for scripting languages. Similar efforts are emerging for Python and Ruby, and TypeScript already has an AOT compiler.

What does this mean?

It means it will be possible to get rid of the PHP VM and JIT in favor of native code packages that can reach maximum performance. It also means that, in the future, PHP may have multiple runtime environments. And it means that if moving to a compiled language is not part of your plans, you risk being left behind.

I urge the entire professional community to take this trend seriously.

https://mp.weixin.qq.com/s/05I3xe4pgRJufSBG-8Gz6w

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

Your SQLite database is silently getting wiped on every Forge deploy
https://laracraft.tech/en/blog/sqlite-on-laravel-forge-with-zero-downtime-deployments

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

PHPverse is back: the free online conference for the whole PHP community on June 9th!
https://jb.gg/w3z4ck

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

PHPverse is back: the free online conference for the whole PHP community on June 9th!
https://jb.gg/w3z4ck

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

PHPverse is back: the free online conference for the whole PHP community on June 9th!
https://jb.gg/w3z4ck

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

Ember: Real-time dashboard for FrankenPHP
https://github.com/alexandre-daubois/ember

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

Generate Apple and Google Wallet passes from Laravel
https://freek.dev/3108-generate-apple-wallet-and-google-wallet-passes-from-laravel

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

What's New in Laravel 13.6: Debounceable Jobs, JSON Health Checks & Cloudflare Email
https://youtu.be/G7W0ynvR2hc

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

Would you be interested in a Laracon Canada?

I’m exploring the idea of a possible Laracon Canada and put together a short interest form to gauge whether there’s enough support to make it happen.

If you’d be interested in participating as an attendee, speaker, sponsor, or organizer, I’d love your input:

**https://laracon.ca**

The form asks about:

where you’re based in Canada
which city you’d be most likely to attend in
what time of year works best
how you’d want to be involved

This isn’t an official announcement, just an attempt to measure real interest and see what a Canadian Laracon could look like.

If this sounds like something you’d want to see, please fill it out and share it around.

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

Open source AST-based code transformation tool for PHP and MCP/automation workflows

I've been working on an open-source tool called **Morfx** and just shipped the first public release.

GitHub:
[https://github.com/oxhq/morfx](https://github.com/oxhq/morfx)

Release:
[https://github.com/oxhq/morfx/releases/tag/v0.1.0](https://github.com/oxhq/morfx/releases/tag/v0.1.0)

The idea is to make automated code edits safer and more targeted.

A lot of AI/code automation workflows still rely on string replacement or full-file rewrites. Morfx is meant to work at the AST level instead, so you can target a specific function, method, class, or file pattern more deterministically.

For PHP specifically, that means things like:

* targeting a single controller method
* replacing or appending code in a scoped way
* querying syntax nodes instead of grepping text
* keeping risky changes stageable/reviewable before applying them

The project exposes the engine through:

* an MCP server
* standalone JSON tools

I think PHP is an especially good fit for this kind of tool because a lot of real-world codebases are large, long-lived, and sensitive to broad automated rewrites.

I'd be interested in feedback on:

* whether this solves a real PHP/Laravel pain point
* what PHP refactor/use cases would matter most
* whether the MCP angle is compelling or if the standalone tools are more useful

Happy to answer technical questions or hear where this falls short.

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

Pratically every Packagist.org project archived + buried at a pyramid in Egypt: Bettergist 2026.Q1, this time with video proof
https://github.com/bettergistco/PackagistArchive/blob/trunk/press-release.md

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

In a Symfony + API Platform project with hexagonal architecture, where do you put validation and how do you handle the DTO vs Command boundary?

I'm trying to figure out the right trade-off between three approaches for write operations. My setup: single-channel HTTP only, synchronous Symfony Messenger bus, no async, no multiple delivery channels.



Approach 1: Separate Input DTO + Command

DTO in Infrastructure with Symfony validator constraints, Processor translates to Command, Command is a pure POPO with no framework dependencies.



Approach 2: Command as API Platform input directly

No separate DTO, validation constraints live on the API resource class, Command stays a pure POPO with zero Symfony/API Platform annotations, Processor enriches with HTTP context

(authenticated user, etc.) before dispatching.



Approach 3: Handler directly as Processor

No Command at all, Handler implements ProcessorInterface, shortest path but Application layer explicitly depends on Infrastructure.

So what approach you recommand please :)





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

TreeTrek: PHP web app for browsing raw Git repos
https://repo.autonoma.ca/treetrek

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

php-deploykit - bash based PHP Deploy tool for Laravel
https://deploykit.nattho.com/

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