I built a PHP 8.4+ radix-tree router with no runtime dependencies and a Laravel-like syntax

Hi guys,
I maintain a private PHP framework (based on Laravel core) called Ariel, where I had been usingpecee/simple-router.

After upgrading the project to PHP 8.4+, I started encountering compatibility warnings. Since its latest stable release appears to date back to December 2023 and the project seems relatively inactive, I decided to replace it rather than maintain framework-specific patches.

I extracted the resulting router into a standalone open-source package:

Ariel Radix Router

The API is intentionally Laravel-like, while the implementation is a small standalone router with no runtime dependencies.

Main features:

radix-tree route matching
static, dynamic and constrained routes
Laravel-like route declarations and groups
cumulative route and group middleware
predictable middleware execution order
named routes and URL generation
scalar-typed controller parameters
compiled route catalogs and optional file cache
explicit middleware lifecycles for persistent workers
support for PHP-FPM, Workerman, RoadRunner, FrankenPHP and similar environments
PHP 8.4+

The package uses PHPUnit, is analysed with PHPStan at the maximum level, and includes reproducible microbenchmarks. I’ve also integrated it back into the original framework and tested persistent request handling and memory stability under Workerman.

It is not intended to be a drop-in replacement for Pecee or Laravel’s router. The goal is to provide a focused, modern router with a familiar API and predictable performance.

I’d particularly appreciate feedback about:

the public API
middleware lifecycle design
missing routing use cases
benchmark methodology
behaviour under long-running workers


I used Codex with GPT-5.6 Sol to help write automated tests, documentation and PHPDoc, run benchmarks, and identify bugs. All resulting changes were reviewed and validated with PHPUnit, PHPStan at the maximum level, integration tests and real Workerman runs.

GitHub: https://github.com/StefanoV1989/ariel-radix-router
Packagist: https://packagist.org/packages/stefanov1989/ariel-radix-router


Thank you in advance,
Stefano.

https://redd.it/1v0ojm3
@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/1v1d0mj
@r_php

Built a Laravel integration for the official Neo4j MCP server (Neo4j Laravel Boost)
/r/mcp/comments/1v1djej/built_a_laravel_integration_for_the_official/

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

Built an email validation service on Laravel + Filament

Sharing because the community here helped me a lot. The whole thing (validation engine, multi-tenant dashboard, queue workers on Horizon) is Laravel + Filament. The dashboard I'd have spent a month on took a few days with Filament.

One thing I learned building it that might interest you: catch-all domains are the bane of email validation because the server says "yes" to every address. But for Microsoft 365 tenants you can hit their GetCredentialType endpoint and it'll actually tell you if a specific mailbox exists, over plain HTTPS, no SMTP. That converted a big chunk of our "unknown" results into real answers.

I also published a Laravel package (`bounceshift/laravel`) with a `Deliverable` validation rule and a facade. It fails open by design, so if our API is down or you're out of credits, it never blocks your flow.

https://bounceshift.com

https://github.com/bounceshift/laravel

Happy to talk through any of the Laravel/Filament decisions.



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

Laravel Tackle: An AI agent harness that lets your Laravel app code and fix itself
https://github.com/jordandalton/laravel-tackle

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

PECL is down?

Cached pages seem fine but release pages like
https://pecl.php.net/rest/r/amqp/stable.txt timeout

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

modyra/modyra: A framework-agnostic, type-safe form engine
https://github.com/modyra/modyra

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

How is Forge?

I've been looking into alternatives for the server management panel I currently use (Ploi), and I am wondering how people that have been using Forge (or used to use it) are finding it nowadays? And if you moved to Forge from Ploi/RunCloud/etc. how does it compare? And if you were using Forge but moved away, why, and to where?

For reference, I have 5 servers, and 28 applications deployed on those combined. I will not be using the Laravel VPS'.


Specifically, how is the Forge experience outside of Laravel deployments and the usage of "Laravel VPS"? While most of my applications are using Laravel, a growing amount are using Next.js or SvelteKit.

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

I built a tool to manage Composer dependencies on WordPress sites without SSH access
https://www.loopress.dev/

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

NO SLEEP - TILL BOSTON
https://redd.it/1v22mh8
@r_php

A pure PHP web server. No nginx, no Apache, no php-fpm.

What if PHP by itself was enough to run a web server?
What if it was actually \*much faster\* than NGINX + PHP-FPM?
And it was \*much safer\* than FrankenPHP or Swoole?

Well, that's exactly that this is. MIT-licensed. Enjoy!

[**https://github.com/Qbix/webserver**](https://github.com/Qbix/webserver)

**Who this is for:**

* PHP Developers who want to host things
* Normies who don't want to install and configure apache/nginx/varnish/go/ssl certificates/mysql/etc.
* People who just get the standalone binary and can host on their computer, without the internet even.

Static file throughput is 55–73% of nginx (C will always beat PHP on raw I/O).

But on actual PHP workloads, the bootstrap savings make this 2–5x faster.

This was taken from the much larger all-in-one PHP platform:

[**https://github.com/Qbix/Platform**](https://github.com/Qbix/Platform)

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

🚀 Introducing URL Image Uploader for FilamentPHP

If you're tired of forcing users to download remote images locally just to re-upload them into your admin panels, I built a custom form component that solves this exact friction: the **URL Image Uploader** package for FilamentPHP.

# ✨ Key Features

Direct Remote Imports: Instantly fetch and attach images directly from any public web link.
Built-in Preview: Gives users an immediate preview before saving to ensure the target URL is correct.
Laravel Storage Integration: Seamlessly saves files straight to your configured storage disk and path.
Image Validation: Validates the link to ensure it targets a readable image format.
Native Look & Feel: Fully compatible with Filament's UI, including dark mode and multilingual setups.

# 📦 Quick Setup & Usage

1. Install via Composer:

composer require amjadiqbal/filament-url-image-uploader


2. Add to your Form Schema:

use Amjadiqbal\FilamentUrlImageUploader\UrlImageUploader;

UrlImageUploader::make('image')
->directory('images');


3. Model Attribute Setup:

use Illuminate\Database\Eloquent\Casts\Attribute;

protected function image(): Attribute
{
return Attribute::make(
get: fn ($value) => $value,
set: fn ($value) => is_array($value) ? $value['image'] : $value,
);
}


🔗 Repositories & Links:

Filament Directory: URL Image Uploader Plugin Page

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

I extracted file-based routing into a standalone PHP package (works in Laravel and Symfony too)

A few weeks ago I posted a small framework here and got a lot of honest feedback. The clearest point, from several people, was that the file-based routing was the interesting part and would be more useful as a standalone library than baked into a whole framework. So I built that.

file-router is a zero-dependency package that maps your directory structure to routes, Next.js style: users/[id].php → /users/{id}, [...slug] for catch-all, route groups, compiled route cache. PHP 8.1+.

The part I think is actually useful: it's framework-agnostic. It runs standalone, but there are thin adapters so it plugs into Laravel (registers as native routes, inherits middleware/container) or Symfony (as a custom route loader, uses Symfony's own matcher and cache). So you can get file-based routing without adopting a new framework.

It's tested across PHP 8.1–8.5, and the migrations in the example template are verified on SQLite, MySQL and Postgres (not assumed; actually run end to end).

Repo: github.com/lizzyman04/file-router

Genuinely looking for feedback again, especially on the adapter approach. Does registering into the host framework's own router feel right to you, or would you expect it to work differently?

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

Quarterly Progress Report - Q2 2026
https://thephp.foundation/blog/2026/07/21/quarterly-report-q2-2026/

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

Pure PHP web+socket server, serves 10x more concurrent PHP than NginX+FPM

# Qbix Server

Yesterday, I posted on Reddit about a web server I launched that's written in pure userland PHP, managed its own preforked workers, and removed the need for NGINX and PHP-FPM.

It was already able to run 10x more concurrent workers (e.g. 1600 workers on an 8GB server).

The biggest bottleneck in PHP hosting is \*memory\*. Each php-fpm worker loads your entire framework independently: 30–60MB per worker. On an 8GB server, that's \~160 workers max. That's your ceiling for concurrent PHP requests.

Well, Qbix Server forks workers \*after\* preloading your classes. Thanks to copy-on-write from the operating system, all that shared code (framework, config, autoloader) uses memory only once. Each worker adds maybe 3-6MB for its per-request data.

This means you get to run 10x more workers, and each worker actually loads much \*faster\* because you don't have to bootstrap your entire framework, config, etc. on every request.

[**https://github.com/Qbix/webserver**](https://github.com/Qbix/webserver)

# But wait... it got faster.

Yesterday, some people were complaining that a userland-PHP server was "only" 70% as fast as NGINX for serving static files. Well, it's 24 hours later, and I'm back, baby! After caching more, it turns out that it's now 25-35% FASTER than NGINX even for static files (as long as you keepalive connections).

Don't believe me? Run the benchmarks. It comes with a test suite now.

# But wait... it now supports sockets

Yes, it is wire-compatible with [socket.io](https://socket.io), and bundles it out of the box (no need for npm). Now you can just drop PHP files into folders, in order to:

1. Handle HTTP Requests. (Cleanup after request is handled.)

2. Handle Web Sockets. (Long-lived, cleanup after disconnect.)

3. Handle Rooms. (Long-lived, cleanup after last websocket leaves.)

In my opinion, the coolest thing is that this retains all the things that made PHP great:

1. Shared-nothing. No way to have memory or secrets leak between requests.

2. Normie-friendly. Just drop files into folders and things just work! No need for hot-reload even. Not even for websockets and rooms -- the old handler will work for the old connections, while the new one is loaded for the new ones.

3. Sequential processing, sure it means you occasionally miss out on fanning out concurrent I/O races, but it's much easier to understand the code.

Give it a try! It's MIT licensed. Enjoy 😄



**Who this is for:**

* PHP Developers who want to host things
* Normies who don't want to install and configure apache/nginx/varnish/go/ssl certificates/mysql/etc.
* People who just get the standalone binary and can host on their computer, without the internet even.

This was taken from the much larger all-in-one PHP platform:

[**https://github.com/Qbix/Platform**](https://github.com/Qbix/Platform)

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

There's no pyenv/nvm equivalent for PHP that works out of the box, so I built one

I wanted something like pyenv or nvm but for PHP. Couldn't find one that actually works the way those do — resolve deps, build from source, switch versions cleanly. The existing options either wrap pre-built binaries or half-ass the dependency resolution.

So I built phpv: https://github.com/supanadit/phpv

`phpv install 8.4` checks your system, builds whatever deps are missing from source, compiles PHP with the right flags. 25 default extensions, out of the box. Supports PHP 4.x through 8.x, version switching, per-project pinning via .php-version, PECL extensions, PHAR tools, portable bundles you can export and import across machines. Linux amd64/arm64 + macOS Intel/Apple Silicon.

Install:

curl -fsSL https://raw.githubusercontent.com/supanadit/phpv/main/install.sh | bash

Then:

eval "$(phpv init bash)"

phpv install 8

Honest con: it compiles from source, so first install is slow. There's no pre-built PHP binary cache yet — working on portable musl-static bundles so you can skip compiling entirely, but that's not done. What's there now works, it just takes a few minutes on first run.

It works. I've been using it on Ubuntu and macOS daily. But I know there are distros and edge cases I haven't hit — Alpine, Arch, weird setups. If you're on any of those, try it and file an issue if it breaks. I want to know.

Repo: https://github.com/supanadit/phpv

Issues: https://github.com/supanadit/phpv/issues

Break it and tell me.

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

New dev building a Laravel + Postgres Attendance & Payroll system — need advice on deployment with strict company control

Hey everyone,

I recently joined a new company as a developer, and I’m building our internal **Attendance and Payroll system** using **Laravel and PostgreSQL**.

Development is going well, but I’m relatively new to deploying Laravel apps in production. I need some guidance on choosing the right hosting and database setup based on my company's requirements:

**App Scope & Needs:**

* **Core Features:** Employee attendance tracking, HR management, and monthly payroll calculation/generation (PDFs, background processing).
* **Database:** Currently using **PostgreSQL** in local development and plan to stick with it.
* **Company Requirement:** Management wants **full control** over the system, server, and employee data (so no fully managed black-box cloud PaaS where we don't control the underlying infrastructure/server location).

**Questions I have for the community:**

1. **Hosting:** Given the need for complete control over the infrastructure, should I spin up a self-hosted VPS (e.g., DigitalOcean, Hetzner, AWS EC2) using **Laravel Forge** or **Coolify**, or setup a bare-metal LEMP stack manually?
2. **Database Setup:** Is running Postgres on the same VPS fine for a small-to-medium internal company tool, or should I decouple it onto its own dedicated instance/managed DB from day one?
3. **Queue & Scheduler:** Since payroll will generate PDFs and queue emails, what’s the best low-maintenance way to handle Laravel queue workers (Supervisor/Redis) and the scheduler in a production environment with complete server access?
4. **Data Protection:** What are the non-negotiables for securing sensitive financial and employee payroll data on a self-hosted server?

Would love to hear how you'd structure this setup! Any tips, common pitfalls, or architectural recommendations are greatly appreciated. Thanks!

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

Removed by Reddit

Removed by Reddit on account of violating the [content policy. ]

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

SymfonyCon Warsaw 2026: 10 easy steps towards a more inclusive workplace
https://symfony.com/blog/symfonycon-warsaw-2026-10-easy-steps-towards-a-more-inclusive-workplace?utm_medium=feed&utm_source=Symfony%20Blog%20Feed

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

A more Laravel-native approach to route localization

About ten months ago I shared [an alternative approach to Laravel route localization](https://www.reddit.com/r/laravel/comments/1n5rhrf/) here. I originally built this for myself and wasn't really expecting a design discussion, but the feedback pushed me somewhere better than where I'd started.

[https://github.com/goodcat-dev/laravel-l10n](https://github.com/goodcat-dev/laravel-l10n)

**TL;DR**

* Route translations live in standard Laravel lang files (`lang/{locale}/routes.php`)
* Localized routes register at boot, so `php artisan route:cache` just works, no custom commands
* URL generation stays on the normal `route()` / `action()` helpers
* Three prefix strategies, plus translated domains
* `L10n::is()`, `hreflang` \+ switcher components, and Ziggy/Wayfinder helpers with SSR

**Route translations now live in standard lang files**

The original post used inline translations. [Someone opened an issue](https://github.com/goodcat-dev/laravel-l10n/issues/1) asking for lang-file support, and I was actually against it at first. But it ended up being a clear improvement: it solved the mess of juggling inline translations across route groups, which had quietly become a nightmare.

Route::get('/example', Controller::class)
->name('example')
->lang(['es', 'it']);

// lang/es/routes.php

return [
'example' => 'ejemplo',
];

**It stays out of the way of the framework**

This is the part I care about most. The localized routes are registered during boot, so Laravel's own route cache works with no custom commands:

php artisan route:cache

And URL generation goes through the normal helpers, there's no separate localized URL API to learn:

// current locale: es
route('example'); // /es/ejemplo
route('example', ['lang' => 'it']); // /it/example
route('example', ['lang' => 'en']); // /example

**Frontend URL generation (Ziggy & Wayfinder)**

Localized routes usually break down once you generate URLs on the frontend. This is the one area I haven't seen other localization packages tackle, so the package ships JavaScript and TypeScript helpers that keep Ziggy's `route()` and Wayfinder calls locale-aware.

**Matching routes across locales**

A comment on the original post pointed out that `routeIs()` gets awkward once localized routes carry different internal names. That's now handled:

L10n::is('example');
L10n::is('admin.*');

It matches the canonical route regardless of the current localized variant.

**Routing strategies**

The package supports three:

* `prefix_except_default`: `/example`, `/es/ejemplo`
* `prefix`: `/en/example`, `/es/ejemplo`
* `no_prefix`: `/example`, `/ejemplo`

The `prefix` variant, which forces a prefix on the default locale too, came out of [another issue](https://github.com/goodcat-dev/laravel-l10n/issues/2).

**Translated domains**

Domains are translated through the same lang files:

return [
'example.com' => 'es.example.com',
'example' => 'ejemplo',
];

This produces `es.example.com/ejemplo`, without adding a redundant locale prefix to the path.

The package is still relatively young and intentionally opinionated. It requires PHP 8.2+ and Laravel 12.44 or 13.

One known trade-off worth calling out up front: `lang` is reserved as the locale-selection parameter, so routes with their own `{lang}` parameter aren't supported by the URL helpers.

Repository: [https://github.com/goodcat-dev/laravel-l10n](https://github.com/goodcat-dev/laravel-l10n)

composer require goodcat/laravel-l10n

That's the update. Any feedback is hugely appreciated, especially from anyone using translated domains, Ziggy, Wayfinder or SSR. Thanks!

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

Files touch() storage implementation for Symfony Lock component
https://github.com/oliezekat/symfony-lock-filetouch

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