php-deploykit - bash based PHP Deploy tool for Laravel
https://deploykit.nattho.com/

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

php-deploykit - bash based PHP deploy tool for Laravel
https://deploykit.nattho.com/

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

Have google search results gone to shit with the advent of AI or am I losing my mind?

This is indirectly related to PHP, evidentely. But the vaat majority of my searches are PHP related.

Just want to make sure it's not only me.

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

New SymfonyCasts Course: Doctrine Inheritance - Class Hierarchy in the Database
https://symfony.com/blog/new-symfonycasts-course-doctrine-inheritance-class-hierarchy-in-the-database?utm_medium=feed&utm_source=Symfony%20Blog%20Feed

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

A local email inbox for Laravel (no Mailtrap/Mailhog needed)
https://redberry.international/mailbox-for-laravel-email-testing/

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

Another PHP deploy app for your VPS

I’d like to show you my new deploy app: deployphp.com. You’re probably thinking, “another deploy app.” Still, I couldn’t resist testing my idea and asking for your feedback. It’s an alternative to Laravel Forge and Ploi, but based on containers. Building and deploying the app all happens on your own server. It’s mainly aimed at PHP applications, but I’ve also added the feature to deploy a Dockerfile (including pulling custom GitHub code). This means you can actually deploy any kind of app.

There is support for migrations, cron jobs, workers, and persistent folders. At the moment, it’s still very experimental, and I’m looking for feedback and testers. Questions about how everything works technically, or suggestions for improvements, are very welcome. I’ve set a limit of 20 users. Preferably keep it constructive 🙂

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

Experience on LunarPHP?

I'm looking into headless ecommerce solutions to build a new shopping site, and found lunarPHP interesting. I searched online to find more information about it like real life projects or sites using it, but can't find much details.

Does anyone have experience using it?

Thanks in advance

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

PHP-Styler: A Back-To-Formula Rewrite
https://pmjones.io/post/2026/04/24/php-styler-a-back-to-formula-rewrite/

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

Introducing Marko: The Truly Modular PHP Framework
https://youtu.be/P_1TtSBQ2vo

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

I spent over a month building a Laravel monorepo

Hi everyone,

My English is not good so I used AI to translate this, sorry about that :)



I have around 6 years of experience with Laravel & Symfony. For the past few years I've been using Botble CMS (you can Google it) to build projects for my customers because it comes with so many built-in features - ACL, form builder, table builder, etc. Building all that myself would probably take a whole year.



But lately I feel like Botble is getting outdated, and the license cost is getting too expensive. So, as the title says, I spent over a month building my own Laravel monorepo (with some help from Claude :D).



So far I have these packages: support, hook system (like WordPress), auth, ACL, settings, i18n, media, form builder, notifications, plugins, themes, self-updater, table builder, menu, and admin panel.



The architecture is modular, each module is a composer package. The packages are loosely coupled, meaning I can use form builder without pulling in table builder, themes, menu, plugins, etc. But form builder does require hook system and support.



I have a couple of questions:

\- Would you actually use something like this? (I want to open source it but I'm a bit nervous, so I figured I'd ask first :D)

\- Is there any feature you think I'm missing or would want me to build? (If I open source this, I'll definitely work on it)



Thanks for reading!

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

PHP 8.5 10 million requests per day with 10 PHP workers on $50 VPS

Drupal 11 website with around 100k requests per day and we previously struggled with consistent performance on 16core 128GB server. New $50 stack is tuned for 100 million requests per day with relying only on PHP 8.5.

Before this stack, we put many layers in front of PHP … Nginx fast-cgi cache, Varnish, Cloudflare HTML caching and tried blocking bots to stop surges but nothing helped.

Irony was server was always on very little CPU usage.

Turns out we were NOT planning our stack for 99% of our traffic - we were planning it for a few surges throughout the day.


New Stack

\- Got rid of Cloudflare, Nginx, Varnish - no external cache in front of PHP

\- Reduced Max PHP workers to just 10 behind Default Apache settings

\- Even turned off Drupal Internal Page Cache and just used Dynamic cache with Memcache support

\- Offloaded all static files via static domain to Cloudfront with a CNAME set up. Default settings - no complexity.

To our surprise, this new set up is blazingly fast, extremely performant and able to scale up to more than 100 requests per second and up to 100 million requests per day.

All 10 php-fpm workers are always warm and even if we get a scraper sending 1000 request in one hit, our set up can absorb it and get back to normal within 10-15 seconds.


And we still have 90% headroom on CPU .. all thanks to latest improvements in PHP performance.

What we have learned!

\- Trust PHP to handle almost everything

\- Plan for 99% of your traffic, not for surge traffic else you will make it worse for 99% of your traffic

\- You don’t need cache layers in front of PHP 8x .. a lot of misconceptions come from PHP 5x era when PHP was slow and CPUs were expensive .. Cache Layers are extra hops and connections and contexts are expensive .. Nginx and Varnish are totally redundant and so are CDNs unless you have lot of global traffic but you will be degrading your local users to some extent.


Don‘t throw extra memory, CPUs, extra workers, external caching in front of PHP unless you have Reddit scale traffic .. make sure your PHP app is properly written (profile custom modules) and trust extremely fast PHP 8x to do the magic!





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

Lens for Laravel v2.0.0 is out: accessibility audits now map Axe-core issues to Blade, React, Vue, and Livewire

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

What if PHP had its own Jupyter Notebook?
https://vimeo.com/1186536132?share=copy&fl=sv&fe=ci

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

Built a Moonshot AI (Kimi K2.6) driver for the new laravel/ai SDK

I just released my first public version of **laravel-ai-moonshot**, an open-source package that adds **Moonshot AI / Kimi K2** support to the official Laravel AI SDK.

GitHub: [https://github.com/jonaspauleta/laravel-ai-moonshot](https://github.com/jonaspauleta/laravel-ai-moonshot)

The goal is simple: use Moonshot/Kimi through Laravel AI’s native provider system instead of building a separate integration.

It supports:

* Text generation
* Streaming responses
* Tool calling
* Image input
* Kimi thinking mode
* Document Q&A via Moonshot Files API
* Per-tier model overrides
* Custom base URL support
* Laravel AI agents, `agent()`, `Ai::textProvider()`, and provider attributes

Install:

composer require jonaspauleta/laravel-ai-moonshot


Basic usage:

use function Laravel\Ai\agent;

$response = agent('You are a helpful assistant.')
->prompt('Explain Kimi K2 in one sentence.', provider: 'moonshot');

echo $response->text;


The package is intentionally strict about what Moonshot supports. No fake embeddings, no fake image generation, no fake provider tools. Unsupported features fail clearly instead of pretending to work.

This is the first clean public release, so feedback is welcome — especially around Laravel package structure, README clarity, edge cases, and real-world Laravel AI usage.

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

I built scout-postgres: a PostgreSQL-native Laravel Scout engine for search without Meilisearch/Algolia/Typesense

I just released **scout-postgres**, an open-source Laravel package I built.

It is a **Postgres-native Laravel Scout engine** that uses PostgreSQL full-text search and `pg_trgm`, so you can add search to Laravel apps without running a separate service like Meilisearch, Algolia, or Typesense.

The goal is not to replace dedicated search engines for every use case. It is for apps where:

* you already use PostgreSQL
* you want Laravel Scout integration
* you need simple, practical search
* you do not want extra infrastructure
* you are okay with Postgres handling the indexing/search side

It supports generated search columns, weighted search vectors, trigram similarity, ranking, filtering, ordering, and normal Scout-style querying.

Repo: [https://github.com/jonaspauleta/scout-postgres](https://github.com/jonaspauleta/scout-postgres)

I would appreciate feedback from Laravel/Postgres people, especially around API design, docs, edge cases, and real-world usage.

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

[Hiring] Senior Platform / DevOps Engineer – Remote or Brussels – PHP/Symfony, Ansible, Linux, PostgreSQL, Nginx – $150k–$180k
/r/devopsjobs/comments/1suq5yx/hiring_senior_platform_devops_engineer_remote_or/

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

I built scout-postgres: a PostgreSQL-native Laravel Scout engine for search without Meilisearch/Algolia/Typesense
/r/laravel/comments/1svihnd/i_built_scoutpostgres_a_postgresqlnative_laravel/

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

Non-incremental sequential IDs using BIGINT?

I've been looking at various ways to obfuscate database IDs to thwart enumeration. Hashids are out because they're not actually secure. UUIDv7 and ULID are good but their length will make for some big indices once you factor in foreign keys too.

Then I had a thought: We're all using BIGINT primary keys these days. A millisecond Unix timestamp easily fits with some headroom. So why not use: [timestamp][randomnumber]?

If we move the epoch from 1970 to 2025, we buy back more space for randomness. With 1,000,000 variations per millisecond, you'll need to be writing >1,000 records per ms for a 50% chance of a collision.

You could go further and just use microseconds and be fine unless you're writing more than 1,000,000,000 records per second somehow. (I suspect some platforms don't advance the clock accurately enough for this, resulting in duplicate times)

For non-mission critical applications that can absorb very occasional collisions, ULID looks overengineered. What do you think?

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