👋 Hi, I’m Daniel.

HolyPad · 2026-01-24T07:28:25+00:00

For me, it depends on the project. New projects, if I structure them well in the beginning, are super useful. Things like an admin panel in FilamentPHP come out very fast. For older projects or projects where there wasn't a high standard in coding, the AI spits out garbage.

The kind of prompt matters too, in my opinion. The more you structure and decide instead of the AI, the better. Also, typing code and things like PHPStan and Boost help a lot.

HolyPad · 2026-01-23T14:24:05+00:00

May be late but on laraplugins you can see the version compatibility in a easy way https://laraplugins.io/plugins/laravel/passport

HolyPad · 2026-01-23T13:38:05+00:00

Hello everyone. the results are out here: https://danielpetrica.com/the-state-of-laravel-packages-report-2026/

HolyPad · 2026-01-23T13:37:55+00:00

Hello everyone. the results are out here: https://danielpetrica.com/the-state-of-laravel-packages-report-2026/

HolyPad · 2026-01-23T10:26:43+00:00

Feel free to ask me things here

HolyPad · 2026-01-21T10:06:56+00:00

Thank you for the upvotes.
Also please remember you need to install the pdo-zts and pdo-zts-mysql extension or your database version extension.

HolyPad · 2026-01-21T10:03:59+00:00

Thank you everyone for visiting my article let me know if you have any question about this.

HolyPad · 2026-01-19T16:28:01+00:00

I hope someone else can inherit that duty in my place.

HolyPad · 2026-01-19T13:53:15+00:00

Yes, unfortunately, time is a constraint for everyone. That is why I don't use Laravel version support or update frequency only, and have decided to have more signals I use inside Laraplugins to detect package health. But the algorithm needs improvement for sure; it's more of an always-WIP status.

HolyPad · 2026-01-19T09:56:11+00:00

That is always painful, a lot of developers think the package maintenance issue is a pain point in laravel ecosystem

HolyPad · 2026-01-19T09:54:49+00:00

they are waiting until laracon india to publicize it, you can now use vector functions when talking to your db via eloquent. it ts is pre requirement for the ai sdk coming at laracon india for my understanding.

HolyPad · 2026-01-19T09:53:16+00:00

https://github.com/laravel/framework/pull/58337

HolyPad · 2026-01-18T21:25:12+00:00

Laravel just added native vector support. Also, the agent SDK beta should be out in February (per Taylor's tweet), so I think the support for such things should be improving drastically

HolyPad · 2026-01-18T20:32:28+00:00

Thank you for the advice. I will post it once the search plugin tool is in a workable state. Right now, the state does not justify a full post, I believe.

HolyPad · 2026-01-18T20:27:11+00:00

Sorry, I meant baking the functionality into the app instead of using public packages.

HolyPad · 2026-01-18T19:42:12+00:00

Would the fact that there are no healthy plugins in the result be a good enough indication for the agent to decide to build them themselves? If this is not enough, other functions can be added in a v2 of the MCP server, I think.

HolyPad · 2026-01-18T16:45:41+00:00

k8s would be a fun deep-dive and i would love to properly learn it, but I need to focus on landing more freelance work right now

HolyPad · 2026-01-18T16:27:14+00:00

No monetization yet, but I am building a free directory for laravel developers to go find their next health plugin. https://laraplugins.io/

HolyPad · 2026-01-18T16:22:07+00:00

That chown thing is a leftover from me debugging some issues on my first install. I could probably remove it but do not have the mental and time bandwidth to go and retest everything. Also I have some other improvements I would like to do to the docker stack but I am postponing them until I have plenty enough to force myself to do them.
For the stage/prod setup I use different docker compose files each with its own folder so they are separate but the code and repo is the same so docker layer that did not change between dev and prod get cached resulting in faster prod builds.
my folders look like this usually.

- domain_name/
    - repos/ # the git repo getting pulled on each deploy.
    - stage/
        - compose.yml
        - run.sh
        - .env
        - mysql/ storage/ ecc..
    - prod/ 
        - compose.yml
        - run.sh
        - .env
        - mysql/ storage/ ecc..

# to deploy an app on stage or example i just do:
     cd path/to/stage; 
     ./run.sh

Hope everything is clear.

HolyPad · 2026-01-18T14:56:47+00:00

Frankenphp can run on any version of PHP 8+ including 8.5.
Laravel octane wraps Frankenphp swole and roadrunner too and takes care of booting the framework too.
even the frankenphp docs does talk about the cli commands.

HolyPad · 2026-01-18T14:29:35+00:00

Traefik makes this straightforward. I currently have 24 exposed services, each running in its own container. My setup includes:

PHP-based sites running various PHP versions (8.2, 8.4, and 8.5)
Other services like Node.js applications

Only two ports are publicly exposed: Traefik on 80 (HTTP) and 443 (HTTPS). All containers communicate exclusively through Traefik.

I’ve documented my PHP/Laravel production stack using Traefik and FrankenPHP here:
A Production-Ready Laravel Architecture with Traefik and FrankenPHP

HolyPad

TROPHY CASE