AnyCable for Laravel: plug-n-play Reverb compatibility and advanced Echo integration
https://evilmartians.com/chronicles/anycable-for-laravel

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

The Laravel Idea Plugin is Now Free for PhpStorm Users | The PhpStorm Blog
https://blog.jetbrains.com/phpstorm/2025/07/laravel-idea-is-now-free/?_cl=MTsxOzE7dlkyeWZyYlVLUWpJS0RISmkwSnNrMWFmZHp6QUZiMHkyN2R5bW1mdHN3Q2RrR3dpUG1INlM0MGVTTEg1dzhzcjs=

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

PHP Website performing down detector

Anyone some info about a (free/opensource) down detecting site that you can install on your now webserver to monitor other servers by answering echo (ping)?

So not to monitor the server itself, but other servers.

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

Is the Composer ecosystem still healthy? 180 MB and 36,000 files for two simple packages.

I just went through a fresh composer require for two packages: microsoft/microsoft-graph and vlucas/phpdotenv. My goal was simple: interact with the Microsoft Graph API and handle environment variables.

After the installation, I was shocked to see my vendor directory had ballooned to 178 MB, containing almost 36,000 files.

This got me thinking: Is this a healthy direction for the PHP ecosystem?

It feels like we're heading straight into the node_modules black hole territory that the PHP/Go community often used to criticize. My fear isn't just the disk space, but the maintenance nightmare this implies. This massive, tangled web of dependencies means a constant stream of updates, potential conflicts, and chasing down bug fixes in packages three or four levels deep.

What happened to the idea of smart, small, self-contained solutions that just work stably for years without constant tinkering? Has the laudable goal of "reusable components" gone too far, leading us to build incredibly fragile towers of dependencies?

What are your thoughts? Is this just the unavoidable price of modern, rapid development, or have we lost our way?

Shouldn't the Log4Shell (CVE-2021-44228) and xz-utils (CVE-2024-3094) cases have made us rethink our approach long ago?

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

VitoDeploy

VitoDeploy is a free, open-source, self-hosted alternative to Laravel Forge, built with Laravel.

Provision servers, deploy apps, manage SSL, workers, cron, and more.
https://laravel-hub.com/blog/vitodeploy-open-source-server-provisioning-deployment

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

The laravel Hub

I’ve recently launched a new platform designed to be a centralized hub for everything related to PHP and Laravel.

Right now, you’ll find curated articles and packages, along with the ability to submit your own Laravel packages.

And this is just the beginning, many more features are coming soon, insha’Allah.

I'd love to hear your thoughts on the project and the idea behind it.
Check it out: https://laravel-hub.com
Follow the updates: https://x.com/TheLaravelHub

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

📢 The Laravel Idea Plugin is Now Free for PhpStorm Users

This is one of the best news I heard recently. Now it's free for phpstorm enabling ultimate ide support for the laravel projects.

https://blog.jetbrains.com/phpstorm/2025/07/laravel-idea-is-now-free/

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

Digital Signatures

Hello everyone,

I have a very specific question about digital signatures. I have a PDF file and its corresponding digital signature generated in the CAdES format (.p7s, detached). What I need now is to embed this signature into the PDF itself, producing a PDF signed in the PAdES format (embedded signature).

Is it technically possible to take a .p7s and the original PDF and generate a new PDF with the signature embedded (PAdES)?

I work with PHP 8.1 and Laravel 9, but I’m open to solutions in other languages (Java, Python, etc.) or tools that perform this conversion. I’ve seen references to the DSS (Digital Signature Services) library by the European Commission, but I’m not sure if it can transform an existing .p7s into a PAdES-signed PDF.

Has anyone done this or can point me in the right direction?

Thanks in advance!\]

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

I built Laravel Backbone – a package that helps you to create structured REST APIs in ~20 lines of code (early beta, feedback welcome)

I built a package called Laravel Backbone (https://github.com/khanhartisan/laravel-backbone) to make building REST APIs in Laravel cleaner and more maintainable, especially for larger projects.

Over time, I kept hitting the same pain points:

Controllers getting packed with repetitive CRUD logic
Scattered model event handling that’s hard to track and maintain
Deleting related data safely often requiring messy, manual steps

With Laravel Backbone, you can:

Spin up a full CRUD endpoint in about 15–20 lines of code
Use lifecycle hooks (before/after store, update, delete) with a simple visitor pattern
A better approach to structure your model event handlers, instead of a long-messy {Model}Observer.php
Handle cascading deletes/restores for SoftDeletes models, no DB constraint headaches
Speed up API testing with built-in CRUD test helpers

I’ve already used this package on a few personal and company projects, and it’s been running reliably.

That said, I’m calling this an early beta – if there’s enough interest and feedback, I’ll put in more time to harden it and release a production-stable version.

Would love to hear your thoughts:

Is this something you’d actually use?
Anything I should rethink or improve before pushing for stable release?

Repo link https://github.com/khanhartisan/laravel-backbone

Comments, issues, or DMs are all welcome – happy to chat with anyone who’s interested.

Thanks for reading – and thanks in advance for your feedback

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

Livewire 4 emoji

Livewire 4 was just announced with the ability to put an emoji on the filename to automatically make it a livewire component, from your components folder.

So what are you guys thinking about this ?

https://preview.redd.it/mgv41nb8o5gf1.png?width=423&format=png&auto=webp&s=59a026cfc143a779c9b137784e1f4607d010ec4a

I don't like it lol I'm gonna stick with the old way if I can

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

Should I implement my own Chat feature (with libsodium) ?

I'm working on a fiverr-like website and contemplating weither or not I should implement a chat feature to simplify communication between freelancers and client.

The interface and web-socket is already set-up, however I'd also like to garantee maximum security/privacy through message encryption, something I know is better done by true professionals.

If I do implement it myself however, I intend on making it extremely limited. It won't be accessible unless there is an active job ongoing, and it won't have any fancy features like vocal message, image uploading or even emojis for that matter, as it's meant to be used strictly to professional ends for now. Users should't have any particular reason to share personal infos and I intend on encouraging them not to.

I've thought about using a third-party bundle as it's clearly the lightest, safest route, but right now the available options (TalkJs, CometChat, ect..) are simply too pricy for me, especially considering how most of it seems to justify itself with a lot of unneeded features.

So my question is : Is my farely basic knowledge of libsodium enough for a light, limited chat feature until I can afford something better or should I skip on it altogether ?

If not implemented there's ways for me to work-around it but I'm afraid users might find the process too steep and get turned off from the plateform as a result.

FYI I'm mostly working with Symfony.

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

One Year of PHP at Scale: Reflections on Community, Research, and Impact

In five days, my newsletter, PHP at Scale, will mark its first year of publication. Reflecting on this milestone, I’ve been considering what creating this newsletter has brought to my work and the PHP community. Here’s my sum up:

* Reddit Discussions: This one is unexpected to me, as I have never used Reddit prior to my newsletter, and was suggested by a colleague that it might be a good place to share my newsletter and insights. Yet the conversation about it here has been the most significant benefit. Your insights and debates have directly inspired some newsletter editions or ideas.
* Research: Second most valuable thing I would say is research. Preparing each issue requires extensive research. This process consistently adds some interesting details my understanding, much like preparing for a technical presentation.
* Newsletter itself: While it’s encouraging to see the number of subscribers and views grow, the newsletter itself hasn’t yet delivered substantial value beyond that metric. I value knowing readers engage with the content, but I’m still seeking deeper interactions or outcomes from it.

I’m interested in your perspectives on creating or engaging with technical content, whether newsletters, blogs, or community discussions. What motivates you to contribute or follow such resources? If you produce content, how do you select topics that resonate? I remain committed to crafting each issue manually, prioritizing authenticity over automated tools, and I’d appreciate your thoughts on this approach or suggestions for future topics.

You can explore my latest insights on scaling PHP applications here: [https://phpatscale.substack.com/p/php-at-scale-11](https://phpatscale.substack.com/p/php-at-scale-11)

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

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

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

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

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

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

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

Global Factory Settings, Better Column Checks & Container Attributes in Laravel 12.21
https://youtu.be/LBadXhqdj1c

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

Multiple Ways to Get Your Domain Name (Host) in Laravel
https://nabilhassen.com/7-ways-to-get-your-domain-name-host-in-laravel

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

Nightwatch has been out for a while, what are your thoughts?

I gave Nightwatch a try for about a month but I eventually moved back to Sentry, the number one reason being the cost. Sentry has stuff I need, like logging and at a much more reasonable price.

I'm not sure what the target audience is for Nightwatch, I use Laravel daily but I felt like it wasn't a good deal compared to other offerings available.

If you're still using Nightwatch, or have used it and switched, why? What are your thoughts on the product?

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

Blaze by Caleb Porzio for blade components speed looks awesome and not just for Livewire
https://youtu.be/GM0glP77tsA?t=20371

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

Asynchronous server vs Coroutine style server in swoole.

I wanted to try and test the basics of Swoole. While reading the documentation on its official site, I noticed there are two ways to write a Swoole HTTP server:

1. Asynchronous server

use Swoole\Http\Server
$http = new Server("127.0.0.1", 9501);
$http->on('request', function ($request, $response) {
$response->end("<h1>Hello Swoole. #".rand(1000, 9999)."</h1>");
});
$http->start();

2. Coroutine style

use Swoole\Coroutine\Http\Server;
use function Swoole\Coroutine\run;
run(function () {
$server = new Server('127.0.0.1', 9502, false);
$server->handle('/', function ($request, $response) {
$response->end("<h1>Index</h1>");
});
$server->handle('/test', function ($request, $response) {
$response->end("<h1>Test</h1>");
});
$server->handle('/stop', function ($request, $response) use ($server) {
$response->end("<h1>Stop</h1>");
$server->shutdown();
});
$server->start();
});

It looks like the asynchronous style is more popular and widely used. However, I wanted to know the differences, challenges, and performance comparisons between these two approaches.

Has anyone tried both methods and found which one is better or more suitable for a large application in production?

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

Why I don't use down migrations
https://freek.dev/2900-why-i-dont-use-down-migrations

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