TOML 1.1 support in PHP
https://www.dereuromark.de/2026/03/30/toml-support-in-php/

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

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/1s7fceb
@r_php

My last project using Laravel : digital business card

https://reddit.com/link/1s7mc09/video/bhl4bryno5sg1/player

You can check it out here : bsncard.com , feedbacks are welcome


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

DDD Was Never the Problem. Your Rules Were.
https://dariuszgafka.medium.com/ddd-was-never-the-problem-your-rules-were-c0fd68cae60e

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

Laracasts

I just started watching lessons for the laravel from scratch on laracasts. Then I saw a yt video of jeff way saying he is stopping. Is it still worth it for me to continue with these lessons or should I just use ai? The video just felt depressing but I still want to do the course. I just wanted to know if I'm wasting time or not.

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

Boosting App Speed with Flexible Caching - Laravel In Practice EP8
https://youtu.be/Z4TRAvRmLrk

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

Alguien con experiencia en Laravel Sail?

Algún diseñador está usando Laravel Sail en vez de WAMP???

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

How can I migrate from apache to nginx in php? I am facing problems doing that, can anybody help??



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

PHP TUI music player.
https://gist.github.com/boukew99/bbfb0b3b43c2dd7094ecb7d510a3356e

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

Coding at the Speed of Thought: The New Era of Symfony Docker
https://dunglas.dev/2026/03/coding-at-the-speed-of-thought-the-new-era-of-symfony-docker/

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

Symfony 6 book

I'm new to Symfony. Is the Symfony book 6 still a good learning resource or should I skip it? I plan to start with version 7.4.

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

Testo (a new testing framework) is now in beta
https://php-testo.github.io/blog/beta-testo

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

Filament Compass: Better LLM prompts for Filament v5
https://github.com/aldesrahim/filament-compass

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

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/1sd8txj
@r_php

Lerd - Local PHP development for Linux
https://geodro.github.io/lerd/

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

Improved markdown quality, code intelligence for 248 formats, and more in Kreuzberg v4.7.0

Kreuzberg v4.7.0 is here. Kreuzberg is an open-source Rust-core document intelligence library with bindings for Python, TypeScript/Node.js, Go, Ruby, Java, C#, PHP, Elixir, R, C, and WASM. 

We’ve added several features, integrated OpenWEBUI, and made a big improvement in quality across all formats. There is also a new markdown rendering layer and new HTML output, which we now support. And many other fixes and features (find them in our the release notes).

The main highlight is code intelligence and extraction. Kreuzberg now supports 248 formats through our tree-sitter-language-pack library. This is a step toward making Kreuzberg an engine for agents. You can efficiently parse code, allowing direct integration as a library for agents and via MCP. AI agents work with code repositories, review pull requests, index codebases, and analyze source files. Kreuzberg now extracts functions, classes, imports, exports, symbols, and docstrings at the AST level, with code chunking that respects scope boundaries. 

Regarding markdown quality, poor document extraction can lead to further issues down the pipeline. We created a benchmark harness using Structural F1 and Text F1 scoring across over 350 documents and 23 formats, then optimized based on that. LaTeX improved from 0% to 100% SF1. XLSX increased from 30% to 100%. PDF table SF1 went from 15.5% to 53.7%. All 23 formats are now at over 80% SF1. The output pipelines receive is now structurally correct by default. 

Kreuzberg is now available as a document extraction backend for OpenWebUI, with options for docling-serve compatibility or direct connection. This was one of the most requested integrations, and it’s finally here. 

In this release, we’ve added unified architecture where every extractor creates a standard typed document representation. We also included TOON wire format, which is a compact document encoding that reduces LLM prompt token usage by 30 to 50%, semantic chunk labeling, JSON output, strict configuration validation, and improved security. GitHub: https://github.com/kreuzberg-dev/kreuzberg. 

Contributions ar always very welcome!

https://kreuzberg.dev/

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

A Week of Symfony #1005 (March 30 – April 5, 2026)
https://symfony.com/blog/a-week-of-symfony-1005-march-30-april-5-2026?utm_medium=feed&utm_source=Symfony%20Blog%20Feed

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

Content negotiation in PHP: your website is already an API without knowing it (Symfony, Laravel and Temma examples)

I'm preparing a talk on APIs for AFUP Day, the French PHP conference. One of the topics I'll cover is content negotiation, sometimes called "dual-purpose endpoint" or "API mode switch."

The idea is simple: instead of building a separate API alongside your website, you make your website serve both HTML and JSON from the same endpoints. The client signals what it wants, and the server responds accordingly.

A concrete use case

You have a media site or an e-commerce platform. You also have a mobile app that needs the same content, but as JSON. Instead of duplicating your backend logic into a separate API, you expose the same URLs to both your browser and your mobile app. The browser gets HTML, the app gets JSON.

The client signals its preference via the Accept header: Accept: application/json for JSON, Accept: text/html for HTML. Other approaches exist (URL prefix, query parameter, file extension), but the Accept header is the standard HTTP way.

The same endpoint in three frameworks

Symfony

<?php

namespace App\Controller;

use Symfony\Bundle\FrameworkBundle\Controller\AbstractController;
use Symfony\Component\HttpFoundation\JsonResponse;
use Symfony\Component\HttpFoundation\Request;
use Symfony\Component\Routing\Attribute\Route;

class ArticleController extends AbstractController
{
#Route('/articles', requirements: ['_format' => 'html|json')]
public function list(Request $request)
{
$data = 'message' => 'Hello World';
if ($request->getPreferredFormat() === 'json') {
return new JsonResponse($data);
}
return $this->render('articles/list.html.twig', $data);
}
}

In Symfony, the route attribute declares which formats the action accepts. The data is prepared once, then either passed to a Twig template for HTML rendering, or serialized as JSON using JsonResponse depending on what the client requested.

Laravel

Laravel has no declarative format constraint at the route level. The detection happens in the controller.

routes/web.php

<?php

use App\Http\Controllers\ArticleController;
use Illuminate\Support\Facades\Route;

Route::get('/articles', ArticleController::class, 'list');

Unlike Symfony, there is no need to declare accepted formats in the route. The detection happens in the controller via expectsJson().

app/Http/Controllers/ArticleController.php

<?php

namespace App\Http\Controllers;

use Illuminate\Http\Request;
use Illuminate\Routing\Controller;

class ArticleController extends Controller
{
public function list(Request $request)
{
$data = 'message' => 'Hello World';
if ($request->expectsJson()) {
return response()->json($data);
}
return view('articles.list', $data);
}
}

The data is prepared once, then either serialized as JSON via response()->json(), or passed to a Blade template for HTML rendering.

Temma controllers/Article.php

<?php

use \Temma\Attributes\View as TµView;

class Article extends \Temma\Web\Controller {
#TµView(negotiation: 'html, json')
public function list() {
$this'message' = 'Hello World';
}
}

In Temma, the approach is different from Symfony and Laravel: the action doesn't have to check what format the client is asking for. Its code is always the same, regardless of whether the client wants HTML or JSON. A view attribute handles the format selection automatically, based on the Accept header sent by the client.

Here, the attribute is placed on the action, but it could be placed on the controller instead, in which case it would apply to all

actions.

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

Optimizing Queries with Memoization - Laravel In Practice EP9
https://youtu.be/A8VfDbbIQxU

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