PHP Reddit – Telegram
PHP Reddit
34 subscribers
294 photos
39 videos
25K links
Channel to sync with /r/PHP /r/Laravel /r/Symfony. Powered by awesome @r_channels and @reddit2telegram
Download Telegram
Disable Zero Downtime Deployments in Forge?

Hello All!

Is the only way to disable the new Zero Downtime Deployments in forge to delete the site + re-create? That seems like a big pain in the neck.

I want to test Laravel Octane so I need to disable ZDD and it seems like it can only be configured on site creation??

https://redd.it/1q8c1qz
@r_php
How are you handling massive build matrices?

I’ve run into a bit of a scaling wall with php-ext-farm and I’m curious how others manage massive build pipelines.

Currently, the build matrix is exploding. I'm building:

160 Base Images: (5 PHP Versions × 8 OS flavors/versions × 4 Platforms)
33,920 Extension Images: (106 Extensions × 2 Versions × 160 Base Images)

As you can imagine, the time to finish a full run is becoming unbearable.

For those of you managing large-scale build combinations, how do you handle/improve this (without going bankrupt) when you need to support multiple versions across different architectures?

https://redd.it/1q8mwzb
@r_php
Developer Experience: Fluent Builder vs. DTO vs. Method Arguments ?

Hello everyone,

I'm currently building a library that fetches data from an (XML) API.

The API supports routes with up to 20 parameters.
Example: /thing?id=1&type=game&own=1&played=1&rating=5&wishlist=0

Now I'm wondering for the "best" way to represent that in my library.
I'm trying to find the best compromise between testability, intuitivity and developer experience (for people using the library but also for me developing the library).

I came up with the following approaches:

## 1. Fluent Builder:

$client->getThing()
->withId(1)
->withType("game")
->ownedOnly()
->playedOnly()
->withRating(5)
->wishlistedOnly()
->fetch();


## 2. DTO:

With fluent builder:

$thingQuery = (new ThingQuery())
->withId(1)
->withType("game")
->ownedOnly()
->playedOnly()
->withRating(5)
->wishlistedOnly();

$client->getThing($thingQuery)


With constructor arguments:

$thingQuery = new ThingQuery(
id: 1,
type: "game",
ownedOnly: true,
playedOnly: true,
rating: 5,
wishlistedOnly: true
);

$client->getThing($thingQuery)


## 3. Method Arguments

$client->getThing(
id: 1,
type: "game",
ownedOnly: true,
playedOnly: true,
rating: 5,
wishlistedOnly: true
);


Which approach would you choose (and why)?
Or do you have another idea?

View Poll

https://redd.it/1q922xx
@r_php
Announcing Kreuzberg v4

Hi Peeps,

I'm excited to announce Kreuzberg v4.0.0.

## What is Kreuzberg:

Kreuzberg is a document intelligence library that extracts structured data from 56+ formats, including PDFs, Office docs, HTML, emails, images and many more. Built for RAG/LLM pipelines with OCR, semantic chunking, embeddings, and metadata extraction.

The new v4 is a ground-up rewrite in Rust with a bindings for 9 other languages!

## What changed:

- Rust core: Significantly faster extraction and lower memory usage. No more Python GIL bottlenecks.
- Pandoc is gone: Native Rust parsers for all formats. One less system dependency to manage.
- 10 language bindings: Python, TypeScript/Node.js, Java, Go, C#, Ruby, PHP, Elixir, Rust, and WASM for browsers. Same API, same behavior, pick your stack.
- Plugin system: Register custom document extractors, swap OCR backends (Tesseract, EasyOCR, PaddleOCR), add post-processors for cleaning/normalization, and hook in validators for content verification.
- Production-ready: REST API, MCP server, Docker images, async-first throughout.
- ML pipeline features: ONNX embeddings on CPU (requires ONNX Runtime 1.22.x), streaming parsers for large docs, batch processing, byte-accurate offsets for chunking.

## Why polyglot matters:

Document processing shouldn't force your language choice. Your Python ML pipeline, Go microservice, and TypeScript frontend can all use the same extraction engine with identical results. The Rust core is the single source of truth; bindings are thin wrappers that expose idiomatic APIs for each language.

## Why the Rust rewrite:

The Python implementation hit a ceiling, and it also prevented us from offering the library in other languages. Rust gives us predictable performance, lower memory, and a clean path to multi-language support through FFI.

## Is Kreuzberg Open-Source?:

Yes! Kreuzberg is MIT-licensed and will stay that way.

## Links

- Star us on GitHub
- Read the Docs
- Join our Discord Server


https://redd.it/1q9stan
@r_php
Generating PDF contracts in Laravel: DomPDF vs Spatie/Browsershot?

I’m building a small app in Laravel to generate and sign contracts.
For the PDF version of those contracts I’ve always used barryvdh/laravel-dompdf and it’s been “good enough”.
Lately I’m seeing more people using Spatie’s Browsershot / laravel-pdf for PDFs.

For a contracts use case (multi-page, decent layout, mostly text with some branding), would you stick to DomPDF or move to Browsershot?
Any real-world pros/cons in terms of CSS support, performance or server setup that I should consider?

https://redd.it/1qa6hgh
@r_php
CKEditor 5 Symfony Integration
https://redd.it/1qanbko
@r_php
Why is something like PHP-FPM necessary in PHP, but not in other languages such as JS (nodejs) or Go lang?

I want to deploy my PHP website on my VPS and thought it would be simpler. I use NGINX as a reverse proxy, and if I want to connect it to PHP, it seems I need something like PHP-FPM, which has several configurations that overwhelm me.



I saw that PHP has a built-in server, but apparently it's only for development and is not recommended for production use. In other environments such as NodeJS or Golang, I don't see the need for another tool like php-fpm. Am I missing something? Maybe there's a simpler way without all the configuration hassle?

https://redd.it/1qagk8i
@r_php
A slightly faster language server for php-cs-fixer

https://github.com/balthild/php-cs-fixer-lsp

It starts php-cs-fixer runners and keep them running in the background. This makes formatOnSave less laggy.

https://redd.it/1qb97qn
@r_php
How do you track temporary workarounds in Laravel projects?

In large Laravel applications, temporary workarounds often turn into permanent technical debt if they aren’t tracked carefully.

One approach is to **mark workarounds with a denoscription and an expiration date using PHP attributes**. With this system, teams can:

* List all workarounds and their current status (healthy or expired)
* Fail CI/CD builds when a workaround has expired
* Provide local feedback when expired code is executed (only in local environments)

Controller classes and methods can be automatically discovered, while other classes (services, jobs, listeners, etc.) can be explicitly enforced where needed.

This strategy helps teams enforce accountability and catch forgotten workarounds before they become problems.

For anyone interested, there’s an open-source implementation here: [https://github.com/medmahmoudhdaya/laravel-deadlock](https://github.com/medmahmoudhdaya/laravel-deadlock)

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