Am I the only a bit sad that there is no more a classic Blade MVC starter-kit?

I skimmed through the new starter kits (React, Vue and Livewire) and I like the idea. I think they partially solve the fragmentation problem and confusion that Breeze + Jetstream caused when first launched.

However, I think that they overcomplicate things and for simple applications they are an overkill. I liked the Blade template for breeze because it was "a breeze" to install and super simple to get started with classic MVC apps. Now there is no more a classic MVC approach and I think it would be great to have that for simpler apps that have a lot of backend logic but not too much reactivity.

What do you think?

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

I've just released v1.0 of Sprout, a multitenancy package for Laravel
https://sprout.ollieread.com/

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

Grapheme: A PHP package to measure the width of unicode strings rendered to a terminal.
https://github.com/soloterm/grapheme

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

Grapheme: A PHP package to measure the width of unicode strings rendered to a terminal.
https://github.com/soloterm/grapheme

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

Are you worried about the Laravel Ecosystem becoming oversaturated?

We've got Livewire, Inertia, Jetstream, Breeze, Volt, Forge, Vapor, Cloud, and the list goes on.

I get that these tools were designed to solve specific problems, but I worry that as the ecosystem continues to grow, the skill requirement to build Laravel applications will continue to grow.

I'm not saying that we need to go back to basics, or that the Laravel community needs to pick a single stack. But with all of the product names being thrown around, I'm starting to see people getting confused.

I feel like this problem gets exasperated when some of these products feel minimally maintained over time. When's the last time we saw a meaningful update to Horizon, Dusk, Pennant, Mix, or Telescope? Did anyone notice that Laravel Spark isn't even in the product list anymore?

I worry that some of the new features and products coming out are hype trains. I get that they provide value and the Laravel team worked hard on them, but will they see significant additional features, or just minimal maintenance?

What are your guy's thoughts on the direction of Laravel in the recent years? Do you guys share the same concerns?

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

Integrating AI into the framework

I was thinking , that AI can integrated in this framework , or other framework, or maybe this thing already exist.
Like for example in debugging, there is an error page that display the error message and file. sometimes it's something simple that a was solved many times ago , and a prompt to ai can solve the problem in minutes.
It can be used to suggest corrections and implement them in a click.

another example is the maker, the code generator , it can be more intelligent , and provide more options to generate every component , improve components , in the command line.

what do you think? is it a good idea? is it something that you would like to see in the future?

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

Filament v4 - overall changes and timeframe?

I could not find any timeline mentioned on the Filament site or the v4 alpha GitHub repo.

Also, I want to confirm before I embark on a large project -

\- I know Filament v3 won't work with Tailwind v4. Should I still start off with Laravel V12, and downgrade Tailwind (which I guess means removing it, then re-installing 3.x, to get it to load as Laravel V11 was doing)? OR, should I only use Laravel V11, for that and maybe other reasons? (I am not sure that I will miss out on anything by using V11, although I'd like to know I'm on the version with the longest support timeframe... then again, V12 is a day old, so it might be foolish to use it now.)

\- will it be hard to update to Filament v4? I didn't have time to read all the changes in GitHub, but it seemed a lot of them are smaller updates, not differences in the way it works.

\- any other tips about anticipating Filament v4 would be useful (any groundbreaking new features, or features or practices that will become discouraged/deprecated)


Thanks to anyone who might know any or some of these answers!

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

Just one month to go before SymfonyLive Paris 2025 workshops begin!
https://symfony.com/blog/just-one-month-to-go-before-symfonylive-paris-2025-workshops-begin?utm_source=Symfony%20Blog%20Feed&utm_medium=feed

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

A closer look at upgrading with the Laravel 12.x Shift

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

About the new starter kits

I have two Laravel projects. One already has Inertia set up with Breeze, while the other only has APIs in the controllers without any frontend setup.

I'm looking for a way (or a tutorial) to install Inertia on the existing API-only project and properly integrate it. Also, for the project that already has Inertia, I want to update the styling and bring in the new design.

Does anyone know the best approach or have any recommended resources for this?

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

What are you thoughts on this Laravel "best practices" article that I see linked every now and again? My personal, albeit small, critique is that it takes subjective opinions and passes them off as how things should always be done. But I'd like to hear your thoughts!
https://github.com/alexeymezenin/laravel-best-practices

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

Laravel Lift alternative

Hi


I've discovered Lift :
Lift is a package that boosts your Eloquent Models in Laravel.

It lets you create public properties in Eloquent Models that match your table schema. This makes your models easier to read and work with in any IDE.

It provides a simple way to set up your models, focusing on simplicity and ease of use by using PHP 8’s attributes.

The package depends on Eloquent Events to work. This means the package fits easily into your project without needing any major changes (unless you’ve turned off event triggering).

However, I've tried to implement in on a model, in an existing project, but I did have an issue with a foreign ID, that I never figured to make working.
Two similar unanswered issues in the github repo makes me think this is either unreliable or abandoned.

Do anyone know and use some equivalent package, that allows to define properties and their attributes (fillable, cast, etc...) directly inside the model ?

If you haven't heard about it, have a look at the docs, or the laravel news blog post that describe it :https://laravel-news.com/laravel-lift. I love the idea of this package, but it seems it needs some polishing...

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

For those using Laravel with Svelte, what’s your stack/workflow like?

I’ve seen two stacks so far:

- Laravel + Inertia with Svelte. The downside seems to be 1) backend and frontend is coupled together (could be a positive). 2) Can’t use SvelteKit

- Separate SvelteKit app consuming an API powered by Laravel



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

A mod that adds saving & reloading to php artisan tinker

I used to use the app https://tinkerwell.app/ until my new company refused to buy it for me! I wanted to recreate the basic work flow of interactive development that tinkerwell provides.

# Without the Mod

Say you are working with a user in tinker:

>$joe = User::where('username', 'joe')->first()
>$joe->fullName
Smith Joe // Oh no! Theres a bug!

Fix the bug:

function getFullNameAttribute() {
return $this->firstname . ' ' . $this->lastname;
}

And tinker is using your old session:

>$joe->fullName
Smith Joe // Oh no! The bug is still there!

In normal Tinker you would have to fix the bug, close the session, reopen the session, and then rerun the query to get $joe again! This makes interactive development difficult and you will find your self Ctrl+C to close, press up to reload previous commands, and repeat.

# With the Mod

>$joe = User::where('username', 'joe')->first()
>$joe->fullName
Smith Joe // Oh no! Theres a bug!

Fix the bug:

function getFullNameAttribute() {
return $this->firstname . ' ' . $this->lastname;
}

Now back to tinker:

>$joe = User::where('username', 'joe')->first()
>$joe->fullName
Smith Joe // Oh no! Theres a bug!
>eval(RELOAD)

INFO Goodbye.

Psy Shell v0.12.4 (PHP 8.4.1 — cli) by Justin Hileman
Tinker Reload Mod
Vars: $joe
> $joe
= App\Models\User {#5175
name: "Joe",
}
> $joe->fullName
Joe Smith

This allows the developer to constantly test and tweak and develop interactively!

This mod saves me at least 30 minutes a day and I love it.

Check it out here: https://github.com/benfaerber/laravel-tinker-reload-mod

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

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

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

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

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

SymfonyLive Paris 2025 : Async avec Messenger, AMQP et Mercure
https://symfony.com/blog/symfonylive-paris-2025-async-avec-messenger-amqp-et-mercure?utm_source=Symfony%20Blog%20Feed&utm_medium=feed

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

How to Run a Laravel Application With Reverb in an Azure Web App
https://cypressnorth.com/web-programming-and-development/how-to-run-a-laravel-application-with-reverb-in-an-azure-web-app/

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

Opensource project with paid version. What workflow?

I have a few personal, private projects (mainly Symfony based) with some commercial potential. I'm considdering releasing a opensource base version, but would also like to explore the possibility of maintaining a paid, more advanced version.

How would one organize the development workflow of something like this? If I were to maintain 2 seperate repositories/codebases, changes affecting both versions would need to be applied to both codebases. Depending on the difference, there might be common parts, parts that behave differently between versions, of parts that are only present in one of the two versions.

I assume some problems can be solved with a good branching strategy in a single repository, others maybe with git submodules. But which would be "leading"? The advanced version that is then stripped down to the base version, of the base version that is then enriched with the advanced features?

I assume there's not single right way to do this, and for me it's a first. So if anyone has done something similar, I would really like to hear your experience with this.

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

Bester Laravel practices — a commentary on the best practices
https://github.com/tontonsb/laravel-bester-practices

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

Choosing a DB for Laravel production

I am relatively new to Laravel and my experience with DB in the past have been small personal projects that ran fine on SQLite. I am planning on launching my first SaaS soon and even though I am not expecting hundreds of thousands of users, it will be more than my previous projects. I have never used a MySQL or Postgres DB before. I have developed my project on my Mac using SQLite, but should I use MySQL or Postgres in production? Will there be hurdles when switching DBs from dev to production? Is there much difficulty in using MySQL instead of SQLite besides the connection environment variables?

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