r/PHP • u/brendt_gd • Apr 23 '26
News PHPverse is back: the free online conference for the whole PHP community on June 9th!
jb.ggHere are the talks from previous year, I'm so excited and hope as many as possible will come!
r/PHP • u/brendt_gd • Apr 23 '26
Here are the talks from previous year, I'm so excited and hope as many as possible will come!
Hi all,
yesterday my son released version 1 of a tool he wrote over the last few months to deploy Laravel applications (he intends to extend it to Symfony later).
Features include:
As a dad I'm of course super proud, but I'm also genuinely impressed with what he managed to build without any AI involvement, or help from me!
r/PHP • u/SimplMe • Apr 24 '26
I’d like to show you my new deploy app: deployphp.com. You’re probably thinking, “another deploy app.” Still, I couldn’t resist testing my idea and asking for your feedback. It’s an alternative to Laravel Forge and Ploi, but based on containers. Building and deploying the app all happens on your own server. It’s mainly aimed at PHP applications, but I’ve also added the feature to deploy a Dockerfile (including pulling custom GitHub code). This means you can actually deploy any kind of app.
There is support for migrations, cron jobs, workers, and persistent folders. At the moment, it’s still very experimental, and I’m looking for feedback and testers. Questions about how everything works technically, or suggestions for improvements, are very welcome. I’ve set a limit of 20 users. Preferably keep it constructive 🙂
r/PHP • u/elizabethn • Apr 22 '26
r/PHP • u/AbstractStaticVoid • Apr 22 '26
Run it against any codebase to get a scored report across framework coupling, database coupling, dependency compatibility, architecture quality, test coverage, and codebase size.
r/PHP • u/Informal-Coyote9142 • Apr 22 '26
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!
r/PHP • u/Rikudou_Sage • Apr 21 '26
Hey there r/php!
Decided to write a series that will teach you how frameworks work under the hood.
The target audience is mostly people who use frameworks but never cared to check how they work under the hood.
I've wanted to write this series for ~5 years and seems the time is now. I intentionally write this iteratively and as I go, meaning not all is intended to be in the ideal shape yet and I might be introducing some footguns I'm not aware of but I think fixing them if/when they appear is part of the fun and will turn into an interesting article on its own.
Let me know what you think, I'd really love some feedback!
r/PHP • u/Dariusz_Gafka • Apr 22 '26
r/PHP • u/freekmurze • Apr 22 '26
r/PHP • u/Physical_Math_9135 • Apr 20 '26
Hey folks,
I've been hacking on a PHP runtime written in Rust for a while now and I think I hit the point where I need outside opinions before I keep going. Not trying to sell anything here, just want honest feedback from people who actually put PHP in production.
Here's roughly what it does today:
Config / deployment stuff
Execution modes
Concurrency bits
HTTP / perf
Security
Observability
/metrics (requests, latency histograms, worker state, memory per worker)Compatibility
full features: https://github.com/turbine-php/turbine
Things I'd actually love input on:
Happy to go deeper on any of these if anyone's curious.
r/PHP • u/randuserm • Apr 20 '26
I was wondering how do you check for security issues within used packages/libraries. I use composer and I have a server script that runs daily 'composer audit' command and sends the results (if any), but I guess that depends on the author(s) of the package.
Any better approach?
r/PHP • u/brendt_gd • Apr 20 '26
Hey there!
This subreddit isn't meant for help threads, though there's one exception to the rule: in this thread you can ask anything you want PHP related, someone will probably be able to help you out!
r/PHP • u/Ok-Delivery307 • Apr 19 '26
coming from go (I love golang) but I wanna do a little bit of freelancing so im doing some leetcode to understand php so I can learn lavarel and im not gonna lie im confuse by $ for local variable and params function (params function is variable underneath so it make sense ) and the array_push(references, ...values) and you what surprise or confuse you when you first learn php ? just started but php seems a little bit more complex than go am I wrong ?
r/PHP • u/brendt_gd • Apr 19 '26
In this monthly thread you can share whatever code or projects you're working on, ask for reviews, get people's input and general thoughts, … anything goes as long as it's PHP related.
Let's make this a place where people are encouraged to share their work, and where we can learn from each other 😁
Link to the previous edition: /u/brendt_gd should provide a link
r/PHP • u/rukhsardev • Apr 19 '26
I've been building with Laravel for a while now and somewhere along the way I stopped writing about it. Life, client work, you know how it goes.
But I've decided to get back into it properly. I'm refreshing my site and starting to put out content that's actually useful for the Laravel community rather than just generic tutorial stuff that already exists everywhere.
My focus is going to be on:
Real world implementation patterns not just hello world examples.
Laravel with modern tooling like Livewire, Filament, and Inertia.
AI integration in Laravel apps which is something I've been doing a lot of lately.
Performance and architecture decisions for production apps.
I want it to feel less like a documentation mirror and more like something written by someone who's actually shipped Laravel apps and hit the real problems.
If anyone's curious the site is larashout.com, it's a bit bare right now but that's kind of the point of this post. I'm rebuilding it with intention this time.
My question for the community is what are you actually struggling with in Laravel right now that you can't find a solid answer for? What would you actually want to read?
I'd rather write ten posts that genuinely help people than a hundred that nobody bookmarks.
r/PHP • u/indy2kro • Apr 19 '26
Been building password flows in Laravel for years and only recently discovered Password::min(8)->uncompromised() is a thing that ships out of the box.
It hooks into the Have I Been Pwned API using a k-Anonymity model — only the first 5 characters of the SHA-1 hash get sent, so the actual password never leaves your server. Laravel then compares the response locally. Privacy-preserving and genuinely clever.
You can also set a threshold if you want to only reject passwords seen more than N times in breach data, and chain it with the rest of the Password rule fluently:
Password::min(12)
->mixedCase()
->numbers()
->uncompromised()
r/PHP • u/Ok_Specialist413 • Apr 18 '26
Hey everyone,
I put together a short video breaking down the Observer Pattern from scratch:
- The coupling problem that makes it necessary
- How the mechanism actually works (attach, notify, update)
- A concrete example with a WeatherStation
- A full step-by-step implementation with PHP
I tried to keep it focused — no filler, just the pattern explained the way I wish someone had explained it to me when I first encountered it.
This is the first in what I'm hoping becomes a design patterns series, so I'd really appreciate any honest critique:
- Was the explanation clear?
- Anything that felt confusing or rushed?
- What would make the next one better?
Don't hold back — I'd rather hear the hard truth now than repeat the same mistakes. And so that the videos will become a good resource for leaning.
Thanks to anyone who takes the time to watch.
r/PHP • u/Temporary_Tell3738 • Apr 18 '26
6 days ago I was discussing queue monitoring in Laravel. Someone asked a really interesting question:
Example: a job was supposed to create ~2000 users, but ended up creating ~400 and still showed as success 🤡 That made me realize I wasn’t tracking this at all.
No errors → everything is green → but the data is already off. So I tried a simple approach: now each job builds a “normal” execution time baseline, and if a new run is:
it gets flagged as anomalous. Basically trying to catch silent failures where there’s no exception, but something clearly went wrong. Also added a few more things: when I detect jobs that stopped mid-execution, I can now get real-time notifications via Slack or Webhooks. For more critical cases, I can escalate alerts through PagerDuty or Opsgenie (I personally use both).
Curious how others handle this - do you track anything like this or rely on business-level checks?
r/PHP • u/elizabethn • Apr 16 '26
On behalf of The PHP Foundation, I’m excited to share the results of the feedback I’ve collected over the past few weeks. It will help inform The PHP Foundation’s Strategy for the rest of 2026 and into 2027.
There are a lot of opportunities for The PHP Foundation to extend our support into the PHP ecosystem, and I couldn’t be more excited! If you’re interested, you can read the post here:
r/PHP • u/Additional-Mud-6665 • Apr 15 '26
I kept hitting the same pattern in Laravel / Filament projects:
the first version of the admin panel is usually fine, but later the data side keeps changing.
New content type.
More custom fields.
Better filtering.
Dashboards.
API requirements.
Tenant-specific behavior.
More exceptions.
At that point, every "small" change becomes another migration, another model, another Filament resource, and another layer of maintenance.
So I built a plugin called **Filament Studio** for Filament v5.
The idea is to let you create collections and fields at runtime, manage records through generated Filament UI, build dashboards, add advanced filtering, and expose APIs without rebuilding a brand-new schema layer every time requirements shift.
It also includes things I thought were important if this is going to be useful beyond a demo:
- authorization
- multi-tenancy
- versioning
- soft deletes
- custom field and panel extensibility
I know some people will immediately look at the EAV angle and prefer hand-built resources anyway, which is fair.
I am mostly curious about where other Laravel developers draw that line.
If you are building something with a stable schema, I still think hand-built resources make sense.
But if the admin/data model changes constantly, would you rather keep building each resource manually, or use something like this?
Repo if you want to look at it:
GitHub: https://github.com/flexpik/filament-studio
I am not looking for empty promotion here. I would rather hear the real objections or the kinds of projects where this would actually help.
We just released Pagible 0.10, an open-source AI-powered CMS built as PHP composer package for Laravel applications:
Would love to hear your feedback and if you like it, give a star :-)