33
Channel to sync with /r/PHP /r/Laravel /r/Symfony. Powered by awesome @r_channels and @reddit2telegram
Shopper v2.9: React and Vue Storefronts
https://laravelshopper.dev/blog/shopper-v2-9-react-and-vue-storefronts
https://redd.it/1u1twiv
@r_php
PHPVerse 2026
/r/TallStack/comments/1u1jie1/phpverse_2026/
https://redd.it/1u1jj0c
@r_php
SymfonyOnline June 2026: Reconfiguring Symfony in real time with sidekicks
https://symfony.com/blog/symfonyonline-june-2026-reconfiguring-symfony-in-real-time-with-sidekicks?utm_medium=feed&utm_source=Symfony%20Blog%20Feed
https://redd.it/1u178tl
@r_php
Is Laravel still worth it in 2026?
/r/webdev/comments/1u14b4w/is_laravel_still_worth_it_in_2026/
https://redd.it/1u14bll
@r_php
PHPverse is starting! Come join thousands of of PHP developers
https://www.youtube.com/watch?v=NR9L0zwXJq4
https://redd.it/1u11u4p
@r_php
Domain-Driven Design
https://slicker.me/php/ddd.html
https://redd.it/1u0vks5
@r_php
Livestream: Outro.fm - Behind the Build w/ Ian Landsman
Outro.fm is a production hub for podcasters who take their show seriously. Rundowns, guest tracking, listener mailbag, and AI-powered show notes all in one place.
I'll be going live tomorrow (6/9) at 12pm EDT (4pm UTC) with Ian Landsman, creator of Outro.fm, to talk about how it was built. We'll be diving into how he used the Laravel AI SDK, Laravel Cloud, and AI for Outro.
Would love to see you there! If you have any questions, feel free to drop them here ahead of time or ask in chat during the stream!
Stream: https://www.youtube.com/watch?v=l9iSi5PfL7A
https://redd.it/1u0n704
@r_php
SymfonyOnline June 2026: Coding at the speed of thought: Symfony DX in 2026
https://symfony.com/blog/symfonyonline-june-2026-coding-at-the-speed-of-thought-symfony-dx-in-2026?utm_medium=feed&utm_source=Symfony%20Blog%20Feed
https://redd.it/1u0a73a
@r_php
Resources for learning microservices in PHP
Hello guys. I want to learn how to build microservices in PHP. I searched on YouTube and Google, but I couldn’t find any good resources.(or I don't understand them well) Does anyone know good courses, tutorials, or materials for learning this? Even GitHub repositories that could help would be appreciated.
https://redd.it/1u03q28
@r_php
A/B Testing for Laravel
https://simplestats.io/blog/ab-testing-for-laravel
https://redd.it/1u02hsm
@r_php
PHP turns 31 🎉today
/r/PHP_Dinos/comments/1u00btw/php_turns_31_today/
https://redd.it/1u00bzy
@r_php
Weekly Ask Anything Thread
Feel free to ask any questions you think may not warrant a post. Asking for help here is also fine.
https://redd.it/1tzw84o
@r_php
Weekly /r/Laravel Help Thread
Ask your Laravel help questions here. To improve your chances of getting an answer from the community, here are some tips:
What steps have you taken so far?
What have you tried from the documentation?
Did you provide any error messages you are getting?
Are you able to provide instructions to replicate the issue?
Did you provide a code example?
Please don't post a screenshot of your code. Use the code block in the Reddit text editor and ensure it's formatted correctly.
For more immediate support, you can ask in the official Laravel Discord.
Thanks and welcome to the r/Laravel community!
https://redd.it/1tzhjk3
@r_php
Stop your parallel agents fighting over one test database — a small Laravel shim
Running multiple coding agents in parallel git worktrees is great until two of them kick off the test suite at the same moment. RefreshDatabase is not polite — it will happily truncate tables mid-run on another worktree’s behalf and you end up chasing flaky failures that aren’t actually in your code at all.
\--parallel doesn’t save you here either, by the way. It isolates workers within a single run but every worktree still shares the same base database name, so you’re right back to two processes scrapping over myapp-test_test_1.
The fix is a small PHP wrapper at bin/test that derives a per-worktree database name from the directory, provisions it if it’s missing (race-safe, via Postgres’ 42P04 handling), and then hands off to artisan with pcntl_exec so exit codes and signals all behave normally. It’s gated behind a single toggle in .env.testing and off by default — CI doesn’t know it exists.
There are also some deliberately paranoid guards: the derived name has to contain the string test or the run aborts outright, because the failure mode otherwise is RefreshDatabase eating your local development data.
Full writeup with the complete wrapper, the TestDatabaseResolver class, and the belt-and-braces safety checks: https://www.mojowill.com/developer/a-test-database-per-worktree/
https://redd.it/1tzjau7
@r_php
A new Markdown parser: I'd appreciate your input!
https://tempestphp.com/blog/tempest-markdown
https://redd.it/1txduop
@r_php
What if you could set breakpoints inside a PHP REPL?
https://www.youtube.com/watch?v=_Blm2Ma6atc
https://redd.it/1u1m10t
@r_php
The Easiest Way to Use MCP Servers in Laravel
https://youtu.be/HVNjNItOP18
https://redd.it/1u1cb48
@r_php
fast_uuid: a near-drop-in ramsey/uuid replacement in pure C, 11-30x faster on the UUIDs Eloquent generates
If you use HasUuids or HasVersion7Uuids on your Eloquent models, every insert mints a UUID through ramsey/uuid, and ramsey/uuid calls random_bytes() once per UUID. That syscall is the bulk of the generation cost. On a write-heavy app, or a batch insert of a few thousand rows, it adds up to a slice of CPU that does nothing but produce identifiers.
I generate a lot of UUIDs, so I wrote a C extension to do it faster.
fast_uuid is a PHP extension (pure C, no C++) covering every RFC 9562 / 4122 version: 1, 2, 3, 4, 5, 6, 7, 8, plus nil and max. The object API mirrors ramsey/uuid under a FastUuid namespace, so for the common case migration is mostly a use swap. Two things make it fast:
- Batched entropy. Instead of one random_bytes() per UUID, it pulls one getrandom() into an 8 KB per-thread buffer and amortizes it across ~500 v4s. The syscall stops dominating.
- A SIMD hex formatter. 16 bytes to 32 hex chars in a handful of vector ops (SSSE3 on x86-64, NEON on ARM64, scalar fallback elsewhere). No build flags.
For UUIDv7 it carries sub-millisecond ordering (RFC 9562 6.2 Method 3), so same-millisecond v7s still sort in insert order, which is the whole point of a v7 primary key for index locality.
Benchmarks vs ramsey/uuid 4.9.2, PHP 8.4.22 NTS non-debug, best of 40 runs (million ops/sec, higher is better): v4 gen 19.5 vs 1.10, v7 gen 19.8 vs 0.66, parse 16.2 vs 3.18. That's ~11-18x on v4, ~18-30x on v7. One honest caveat: fast_uuid per-op time is ~50 ns, low enough that scheduler noise dominates a single run, so read its numbers as order-of-magnitude (±10% run-to-run). ramsey/uuid reproduces to within ~3%.
Before you swap, two notes. The FastUuid\Compat layer isn't on Packagist yet (install it as a Composer path repository for now), and a custom random or time generator intentionally routes off the C fast path, same as ramsey/uuid. There's also a uuid_v4_fast() using a non-crypto PRNG for non-security IDs only.
Install: pie install iliaal/fast_uuid
https://github.com/iliaal/fast_uuid
Happy to answer questions, especially from anyone running UUIDv7 primary keys at volume.
https://redd.it/1u14xzm
@r_php
PagibleAI CMS 0.11 — an AI-native, Laravel-first CMS with real-time collaboration and themes
https://redd.it/1u10yg0
@r_php
The Anti-Corruption Layer: Protecting Your Domain from External APIs
https://redd.it/1u0zss2
@r_php
Does anyone use Polyscope from BeyondCode?
I've been using it off and on for a few months. Overall I like it.
Anyone else using it? Opinions? I noticed there is a recent GH thread about the lack of support for free and paid users. Is that real or just noise?
Product: https://getpolyscope.com/
https://redd.it/1u0o2h7
@r_php
I built an attribute-driven lexer/parser library for PHP and would love API feedback
https://github.com/edin/lexicon
https://redd.it/1u0env6
@r_php
Built a free Claude Code skill for Laravel dependency triage — useful or nah?
I want to build an open library of Claude Code skills focused on **Laravel project maintenance** the boring-but-painful stuff: keeping deps healthy, triaging updates, prepping framework upgrades. One library, you grab whichever skill you need.
I started with a skill that came straight out of my own pain. On an older project I had `composer outdated` and `composer audit` throwing a wall of red at me but no priority, no *"which of these actually matters today"*, and zero help when a package was just abandoned (Composer literally says "no replacement was suggested" and leaves you googling).
**The problem the first skill solves:** it reads your real Composer output and turns it into a plan.
* Flags each dep: 🔴 vulnerable / 🟠 abandoned / 🟡 major / 🟢 safe
* Suggests a maintained replacement for abandoned packages
* Finds the smallest CVE fix (e.g. *"2.0.30 → 2.0.54 drop-in, don't jump to 3.x"*)
* Checks PHP/Laravel compat before any major
* Outputs a **Do-now / Do-carefully / Defer** plan
It's **advise-only** read-only, never touches your `composer.json` or code.
Repo: [https://github.com/ArtemProshkovskiy/laravel-maintenance-skills](https://github.com/ArtemProshkovskiy/laravel-maintenance-skills)
**What I'm really asking:**
1. What do you think of the library idea overall is Laravel maintenance something you'd want skills for, or not really?
2. Thoughts on this first skill specifically?
3. If you've got interesting ideas for what the next skill should tackle, I'm all ears.
Trying to figure out if this is worth pouring time into. Honest takes very welcome 🙏
https://redd.it/1u06heb
@r_php
SymfonyOnline June 2026: Dealing with audit logs
https://symfony.com/blog/symfonyonline-june-2026-dealing-with-audit-logs?utm_medium=feed&utm_source=Symfony%20Blog%20Feed
https://redd.it/1u03c58
@r_php
Weekly help thread
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!
https://redd.it/1tzzd5s
@r_php
QUESTION - How do you secure your PHP source code before sending to the client/customer?
I was wondering how you secure your source code (PHP, Laravel, etc) from being exposed? I've seen some paid version like SourceGuardian, IonCube and most of them are starting at $249 which is huge. How are you handing such security concerns?
I want to build the robust and secured app vault platform that I can use to protect and not expose any source code to client.
https://redd.it/1tzyscb
@r_php
Why does PHPStan think $user->emailverifiedat is a string when it's cast to datetime?
Ran into this on a default Laravel 11+ model and figured it's worth writing up — it hits anyone using the casts() method form.
Stock User, cast where Laravel puts it now:
protected function casts(): array
{
return
'email_verified_at' => 'datetime',
'password' => 'hashed',
;
}
Read the attribute, null check and all:
public function render(User $user): string
{
$verifiedAt = $user->emailverifiedat;
if ($verifiedAt !== null) {
return 'Verified on ' . $verifiedAt->format('M j, Y')
}
return 'Not verified yet';
}
larastan, level 6:Cannot call method format() on string.
string, on a datetime cast, after a null check. The error gives you the type at the call site and nothing about where it came from.
I maintain a small phpstan extension for exactly that blind spot — it prints every event that shaped a value up to a line instead of only the final mismatch. Traced the variable:
$verifiedAt · render app/Services/VerifiedBadge.php (up to L16)
──────────────────────────────────────────────────────────────
L13 assign string|null
L16 narrow $verifiedAt !== null => string
L16 read string
──────────────────────────────────────────────────────────────
3 events · final type: string
So the !== null was never the issue — it was string|null the moment it got assigned on L13, never a Carbon. The lie is upstream, in the property. Pointed it there:
$user->emailverifiedat · render app/Services/VerifiedBadge.php (up to L13)
──────────────────────────────────────────────────────────────
L13 read string|null via ModelPropertyExtension
──────────────────────────────────────────────────────────────
1 event · final type: string|null
via ModelPropertyExtension — not my code, not PHPStan core, it's larastan's model reflection deciding string|null. That's the thread to pull. In larastan's source:
it builds the model with new Instance WithoutConstructor(), so getCasts() comes back without the casts() method applied. It tries to recover it, but by default (parseModelCastsMethod: false) it reads the declared return type of casts() — which on the stock model is array<string, string>, a genericarray, not the literal ['email_verified_at' => 'datetime'\].
A generic array isn't a constant array, so the method casts get dropped and it falls back to the DB column type. timestamp nullable → string|null.
One line:
parameters:
parseModelCastsMethod: true
and the property goes back to what you'd expect:
$user->emailverifiedat · render app/Services/VerifiedBadge.php (up to L13)
──────────────────────────────────────────────────────────────
L13 read Carbon\Carbon|null via ModelPropertyExtension
──────────────────────────────────────────────────────────────
1 event · final type: Carbon\Carbon|nullfalse is a defensible default for analysis speed, and it's a 5-second fix once you know it's there. The gap is between the error and that knowledge. format() on string gives you nothing to grep; via ModelPropertyExtension gives you the file to open.\PHPStan\dumpType() exists, used it for years. It prints the type at one spot — it won't show you the value was already wrong at the assign two lines up, and it won't name the extension that produced the type, which on Laravel is the part I'm always missing.
The tool does $var, $obj->prop, self::$static, with param / assign / assign-op / narrow / read events, --json for scripting, and a PhpStorm plugin if you'd rather drop a caret on a variable than type a path.
repo: https://github.com/kayw-geek/phpstan-type-trace
https://redd.it/1tzvpht
@r_php
[Showcase] I tried to learn MVC and modularity using JSON by creating Pokémon in pure PHP.
Well, it's kind of a bummer that I can't post images here ;-;
But basically, the project is a CLI Pokémon battle system. I've been working on it on weekends after work, and it's a simple project I'm doing for practice.
The code is organized using MVC—Model, View, Controller. You can easily import moves and Pokémon using a JSON file.
It follows the turn-based battle format, but it’s still a pretty limited system—no differentiation between Special Defense, Special Attack, accuracy, or types—because honestly, it was already taking up too much of my time, and Pokémon has probably the most complex battle system and “what-if” scenarios I’ve ever seen o_O
I hope you like it; there are some simple screenshots on GitHub: https://github.com/MarujoEn/php_pokebattle_study
Obviously, any feedback is appreciated, especially regarding understanding structures and object-oriented programming, rather than me continuing to create everything in a single file.
:3
https://redd.it/1tzmmp1
@r_php
Free Laravel 11 & 12 Notes for Beginners | Laravel Tutorial, Cheat Sheet & Learning Guide
I created a comprehensive Laravel 11 & Laravel 12 learning guide and made it available for free.
These notes are designed for beginners, PHP developers, backend developers, and anyone learning modern Laravel development.
Topics Covered:
• Laravel Installation & Setup
• Blade Templates
• Routing
• Controllers
• Request Validation
• Database Migrations
• Database Seeders
• Query Builder
• Eloquent ORM
• CRUD Operations
• One-to-One Relationships
• One-to-Many Relationships
• Many-to-Many Relationships
• Polymorphic Relationships
• JSON Columns
• Accessors & Mutators
• Query Scopes
• Model Events
• Observers
• Middleware
• Sessions
• Authorization Gates
• Policies
• File Uploads
• Mail
• Laravel Sanctum
• REST API Development
• API Authentication
• Postman Testing
Available Formats:
• PDF
• notes.md
• llms.txt (LLM-friendly version)
GitHub Repository:
https://github.com/Kumaravi-admin/developer-notes/tree/main/Laravel
Complete Developer Notes Repository:
https://github.com/Kumaravi-admin/developer-notes
Who is this for?
• Laravel Beginners
• PHP Developers
• Backend Developers
• Full Stack Developers
• Students Learning Laravel
• Developers Preparing for Interviews
https://redd.it/1tzfvqv
@r_php
I built debugd, a tiny request profiler for Laravel you actually leave running
A live UI (Go binary or cross-platform desktop app, macOS/Windows/Linux) plus a --dev Composer package that quietly ships each request's queries, logs, timings, and exceptions to it. No Docker, no database, no config.
\- Every request live: method, path, status, time, query count
\- N+1 detection that suggests the actual ->with('…') to add
\- Query waterfall + where each query fired from
\- debugd() helper for dumps/benchmarks — no-op in prod
\- Octane/FrankenPHP-safe; tails storage/logs too
composer require --dev debugd/debugd-laravel
Inert unless you set DEBUGD_HOST, so safe to leave installed. MIT.
👉 https://github.com/ShahramMebashar/debugd
https://redd.it/1txcegs
@r_php