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/1pgoukp
@r_php
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/1pgoukp
@r_php
Laravel
Installation - Laravel 12.x - The PHP Framework For Web Artisans
Laravel is a PHP web application framework with expressive, elegant syntax. We’ve already laid the foundation — freeing you to create without sweating the small things.
Yii Database abstraction 2.0
The second major version of Yii Database abstraction was released. The package is framework agnostic and thus can be used with any framework or without one. Supported databases are MSSQL, MySQL, MariaDB, Oracle, PostgreSQL, and SQLite. As usual with Yii3 packages, all the code is totally covered in types and the unit tests and has a high mutation testing score.
New Features
\- Implement
\-
\-
\-
\- New conditions:
\- PHP backed enums support
\- User-defined type casting
\-
Enhancements
\- Optimized SQL generation and query building
\- Improved type safety with psalm annotations
\- Method chaining for column classes
\- Better exception messages
\- Refactored core components for better maintainability
\- PHP 8.5 support
https://github.com/yiisoft/db
https://redd.it/1pgsl08
@r_php
The second major version of Yii Database abstraction was released. The package is framework agnostic and thus can be used with any framework or without one. Supported databases are MSSQL, MySQL, MariaDB, Oracle, PostgreSQL, and SQLite. As usual with Yii3 packages, all the code is totally covered in types and the unit tests and has a high mutation testing score.
New Features
\- Implement
ColumnInterface classes according to the data type of database table columns for type casting performance.\-
ConnectionProvider for connection management\-
ColumnBuilder for column creation\-
CaseX expression for CASE\-WHEN\-THEN\-ELSE statements\- New conditions:
All, None, ArrayOverlaps, JsonOverlaps\- PHP backed enums support
\- User-defined type casting
\-
ServerInfoInterface and its implementationEnhancements
\- Optimized SQL generation and query building
\- Improved type safety with psalm annotations
\- Method chaining for column classes
\- Better exception messages
\- Refactored core components for better maintainability
\- PHP 8.5 support
https://github.com/yiisoft/db
https://redd.it/1pgsl08
@r_php
Yii Framework
Yii Database 2.0 + Drivers
How are you managing Stripe subnoscriptions & plans inside Laravel?
I’m working on a new Laravel app and once again running into my usual pain point: managing Stripe subnoscription plans from inside my own admin panel instead of relying only on env files + the Stripe dashboard.
I’m curious how others are handling this in real projects:
Do you create/manage products and prices directly from your Laravel admin?
Are you storing plans in the database and syncing to Stripe?
How do you handle discounts, promos, and free trials in a clean way?
Any patterns that didn’t work well for you?
Not looking for a full tutorial—just want to see real-world approaches and tradeoffs. Screenshots, code snippets, or repo links are welcome if you’re willing to share.
https://redd.it/1ph1jgi
@r_php
I’m working on a new Laravel app and once again running into my usual pain point: managing Stripe subnoscription plans from inside my own admin panel instead of relying only on env files + the Stripe dashboard.
I’m curious how others are handling this in real projects:
Do you create/manage products and prices directly from your Laravel admin?
Are you storing plans in the database and syncing to Stripe?
How do you handle discounts, promos, and free trials in a clean way?
Any patterns that didn’t work well for you?
Not looking for a full tutorial—just want to see real-world approaches and tradeoffs. Screenshots, code snippets, or repo links are welcome if you’re willing to share.
https://redd.it/1ph1jgi
@r_php
Reddit
From the laravel community on Reddit
Explore this post and more from the laravel community
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/1ph2xsd
@r_php
Feel free to ask any questions you think may not warrant a post. Asking for help here is also fine.
https://redd.it/1ph2xsd
@r_php
Reddit
From the symfony community on Reddit
Explore this post and more from the symfony community
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/1ph5x52
@r_php
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/1ph5x52
@r_php
Reddit
From the PHP community on Reddit
Explore this post and more from the PHP community
soo the thing i anticipate the most has been asleep for 3 months. is it finished and just waiting for juicy release date? what do you think?
https://redd.it/1ph76g5
@r_php
https://redd.it/1ph76g5
@r_php
[Research] Tool to Trace Model and Event Usage in Laravel Projects
I'm working on a tool that shows how models get used in a Laravel project, but in a way normal users can understand. Kind of like PhpStorm’s "find usages", but shown in a simple dashboard for managers or anyone who isn't deep into the code
The idea is that you click a model or a method and see the path of what touches it: `action → controller → route`. I want to do the same for listeners, jobs, events, and anything else that runs when something happens in the app
Basically I want to answer things like:
* what happens when a user gets created
* which listeners run when a user is updated
* which jobs fire when a post is created
I'm trying to figure out if this would be useful for others as an open-source tool. You would import your Laravel project into it and get all these insights about what cals what and what runs when things happen
https://redd.it/1phe7ua
@r_php
I'm working on a tool that shows how models get used in a Laravel project, but in a way normal users can understand. Kind of like PhpStorm’s "find usages", but shown in a simple dashboard for managers or anyone who isn't deep into the code
The idea is that you click a model or a method and see the path of what touches it: `action → controller → route`. I want to do the same for listeners, jobs, events, and anything else that runs when something happens in the app
Basically I want to answer things like:
* what happens when a user gets created
* which listeners run when a user is updated
* which jobs fire when a post is created
I'm trying to figure out if this would be useful for others as an open-source tool. You would import your Laravel project into it and get all these insights about what cals what and what runs when things happen
https://redd.it/1phe7ua
@r_php
Reddit
From the PHP community on Reddit
Explore this post and more from the PHP community
Migrating our multi-tenant Laravel app to AWS ECS with minimal impact
https://youtu.be/SxXW4H1y4xY
https://redd.it/1phdtel
@r_php
https://youtu.be/SxXW4H1y4xY
https://redd.it/1phdtel
@r_php
YouTube
Rebuilding our infrastructure from scratch and migrating live (AWS ECS migration)
#laravel #cloudflare #aws #infrastructure #terraform
It’s been a busy few months in which I was finally able to migrate our entire application to AWS from our current cloud provider. We were able to do this migration without any major disruptions for our…
It’s been a busy few months in which I was finally able to migrate our entire application to AWS from our current cloud provider. We were able to do this migration without any major disruptions for our…
PhpStorm 2025.3 Is Now Out: PHP 8.5 support, Laravel Idea integrated, Pest 4 Support
https://blog.jetbrains.com/phpstorm/2025/12/phpstorm-2025-3-is-now-out/
https://redd.it/1phgqxd
@r_php
https://blog.jetbrains.com/phpstorm/2025/12/phpstorm-2025-3-is-now-out/
https://redd.it/1phgqxd
@r_php
The JetBrains Blog
PhpStorm 2025.3 Is Now Out | The PhpStorm Blog
Welcome to PhpStorm 2025.3! This release brings native Claude Agent integration, out-of-the-box Laravel support, support for PHP 8.5, improvements in generics, a new Islands theme, and more.
PhpStorm 2025.3 now includes Laravel support out-of-the-box, fully integrating the features of the Laravel Idea plugin
https://www.jetbrains.com/phpstorm/whatsnew
https://redd.it/1phkjz3
@r_php
https://www.jetbrains.com/phpstorm/whatsnew
https://redd.it/1phkjz3
@r_php
JetBrains
What's New in PhpStorm 2025.3
Explore what's new in PhpStorm 2025.3, including PHP 8.5 support, out-of-the-box Laravel support, and multi-agent experience in JetBrains AI.
Now Open Source: Beacon: Feature Flag Management for Laravel/Pennant
https://github.com/beacon-hq/app
https://redd.it/1phm57w
@r_php
https://github.com/beacon-hq/app
https://redd.it/1phm57w
@r_php
GitHub
GitHub - beacon-hq/app
Contribute to beacon-hq/app development by creating an account on GitHub.
🚀 Bare Metal PHP: a very lightweight PHP framework with a Go-powered app server (fast workers + slow workers, hot reload, persistent PHP workers)
I’ve been teaching myself framework design and accidentally built something weird (PHP framework + Go app server). It started off as a lightweight Laravel clone -- I wanted to create something with the feel of
Hey everyone — I’m still pretty new to framework architecture and backend engineering in general, so please go easy on me 😅
I’ve been building a PHP framework *just so I could understand how Laravel/Symfony/etc. actually work under the hood*. This was supposed to be a small personal learning project… but it sort of spiraled into something more interesting, and I’m honestly unsure if I’ve built something cool or wasted a *ton* of time.
I just released **Bare Metal PHP v0.2.0**, and the part I’m most unsure/excited about is:
# I wrote a Go application server that runs PHP through persistent workers
I started looking into Swoole/RoadRunner, but thought it would be interesting/cool to build a Go app server built-in to the PHP framework without needing to install a binary or configure extensions.
So I wrote a Go front-end server that:
* keeps a pool of persistent PHP workers alive
* routes “slow” requests (uploads, reports, heavy endpoints) to a separate pool
* supports automatic hot reload
* serves static files instantly
* talks to PHP using a binary header + JSON payload bridge
You can install it via:
php mini go:install
go mod tidy
php mini go:serve
Before this, I had never written anything serious in Go OR designed a worker protocol, and my primary goal was just to mess around and learn new things, which I definitely have. I'm looking for some feedback on what direction I could take this.
**What the framework itself includes:**
It’s still early, but right now it has:
* routing + controller auto-resolution
* requests/responses
* view layer
* migrations + rollback batches
* SQLite/MySQL/Postgres support
* simple service container
* artisan-like console (`php mini`)
* full PHPUnit test suite (176 tests atm)
Skeleton app installs via:
composer create-project baremetalphp/baremetalphp myapp
Framework code is here:
[**https://github.com/baremetalphp/framework**]()
Docs are here:
[**https://baremetalphp.com**]()
tbh, just looking for some honest feedback :)
Hey everyone — I’m still pretty new to framework architecture and backend engineering in general, so please go easy on me 😅
This whole project started because I wanted to understand how Laravel, Symfony, etc. actually work under the hood. I planned to build a tiny Laravel-ish clone just for learning… but it spiraled into something much bigger, and now I’m honestly not sure if I built something cool or if I just wasted a ton of time.
I just released BareMetalPHP v0.2.0, and the part I’m most unsure/excited about is this:
# ⭐ I wrote a Go application server that runs PHP through persistent workers
I had been reading about RoadRunner and Swoole, but I thought it would be fun (and educational) to try building a Go app server built directly into the PHP framework, without needing to install any external binaries or PHP extensions.
So I ended up writing a Go front-end server that:
* keeps a pool of persistent PHP workers alive
* separates “slow” requests (uploads, reports, heavy endpoints) into their own worker pool
* supports automatic hot reload
* serves static files extremely fast
* communicates with PHP using a simple binary header + JSON payload protocol
You can try it out with:
php mini go:install
go mod tidy
php mini go:serve
Before this I had never written anything serious in Go or designed a worker protocol, and the main goal was just to learn — which I definitely did. Now I’m trying to figure out what direction (if any) this should go next.
# What the framework currently includes:
It’s still early, but right now Bare Metal PHP has:
* routing + controller auto-resolution
* requests / responses
* a simple view layer
* migrations + rollback batches
* SQLite /
I’ve been teaching myself framework design and accidentally built something weird (PHP framework + Go app server). It started off as a lightweight Laravel clone -- I wanted to create something with the feel of
Hey everyone — I’m still pretty new to framework architecture and backend engineering in general, so please go easy on me 😅
I’ve been building a PHP framework *just so I could understand how Laravel/Symfony/etc. actually work under the hood*. This was supposed to be a small personal learning project… but it sort of spiraled into something more interesting, and I’m honestly unsure if I’ve built something cool or wasted a *ton* of time.
I just released **Bare Metal PHP v0.2.0**, and the part I’m most unsure/excited about is:
# I wrote a Go application server that runs PHP through persistent workers
I started looking into Swoole/RoadRunner, but thought it would be interesting/cool to build a Go app server built-in to the PHP framework without needing to install a binary or configure extensions.
So I wrote a Go front-end server that:
* keeps a pool of persistent PHP workers alive
* routes “slow” requests (uploads, reports, heavy endpoints) to a separate pool
* supports automatic hot reload
* serves static files instantly
* talks to PHP using a binary header + JSON payload bridge
You can install it via:
php mini go:install
go mod tidy
php mini go:serve
Before this, I had never written anything serious in Go OR designed a worker protocol, and my primary goal was just to mess around and learn new things, which I definitely have. I'm looking for some feedback on what direction I could take this.
**What the framework itself includes:**
It’s still early, but right now it has:
* routing + controller auto-resolution
* requests/responses
* view layer
* migrations + rollback batches
* SQLite/MySQL/Postgres support
* simple service container
* artisan-like console (`php mini`)
* full PHPUnit test suite (176 tests atm)
Skeleton app installs via:
composer create-project baremetalphp/baremetalphp myapp
Framework code is here:
[**https://github.com/baremetalphp/framework**]()
Docs are here:
[**https://baremetalphp.com**]()
tbh, just looking for some honest feedback :)
Hey everyone — I’m still pretty new to framework architecture and backend engineering in general, so please go easy on me 😅
This whole project started because I wanted to understand how Laravel, Symfony, etc. actually work under the hood. I planned to build a tiny Laravel-ish clone just for learning… but it spiraled into something much bigger, and now I’m honestly not sure if I built something cool or if I just wasted a ton of time.
I just released BareMetalPHP v0.2.0, and the part I’m most unsure/excited about is this:
# ⭐ I wrote a Go application server that runs PHP through persistent workers
I had been reading about RoadRunner and Swoole, but I thought it would be fun (and educational) to try building a Go app server built directly into the PHP framework, without needing to install any external binaries or PHP extensions.
So I ended up writing a Go front-end server that:
* keeps a pool of persistent PHP workers alive
* separates “slow” requests (uploads, reports, heavy endpoints) into their own worker pool
* supports automatic hot reload
* serves static files extremely fast
* communicates with PHP using a simple binary header + JSON payload protocol
You can try it out with:
php mini go:install
go mod tidy
php mini go:serve
Before this I had never written anything serious in Go or designed a worker protocol, and the main goal was just to learn — which I definitely did. Now I’m trying to figure out what direction (if any) this should go next.
# What the framework currently includes:
It’s still early, but right now Bare Metal PHP has:
* routing + controller auto-resolution
* requests / responses
* a simple view layer
* migrations + rollback batches
* SQLite /
MySQL / Postgres support
* a lightweight service container
* an artisan-style console (php mini)
* a full PHPUnit test suite (176 tests so far)
Skeleton app install:
composer create-project baremetalphp/baremetalphp myapp
Code: [https://github.com/baremetalphp/framework](https://github.com/baremetalphp/framework)
Docs: [https://baremetalphp.com](https://baremetalphp.com)
I’m posting this mainly because I’d love honest feedback — good or bad.
I’m still learning, so if I made awful architectural decisions or reinvented things poorly, I'd genuinely appreciate hearing it.
Thanks for reading 🙏
https://redd.it/1phoz2m
@r_php
* a lightweight service container
* an artisan-style console (php mini)
* a full PHPUnit test suite (176 tests so far)
Skeleton app install:
composer create-project baremetalphp/baremetalphp myapp
Code: [https://github.com/baremetalphp/framework](https://github.com/baremetalphp/framework)
Docs: [https://baremetalphp.com](https://baremetalphp.com)
I’m posting this mainly because I’d love honest feedback — good or bad.
I’m still learning, so if I made awful architectural decisions or reinvented things poorly, I'd genuinely appreciate hearing it.
Thanks for reading 🙏
https://redd.it/1phoz2m
@r_php
GitHub
GitHub - baremetalphp/framework
Contribute to baremetalphp/framework development by creating an account on GitHub.