New PostgreSQL Client/Parser/QueryBuilder library
Hey everyone!
I would like to share our recent addition to Flow PHP framework, a brand new PostgreSQL library based on ext-pgsql and pganalyze/libpg_query
Doctrine DBAL is awesome! But since it's database engine agnostic, it's missing some nice features like for example, query builder is not covering all db specific features like CTE.
This makes us to either keep SQL queries as plain strings, or make some tradeoffs while using Query Builder, flow-php/postgresql covers this gap providing probably the most advanced query builder in PHP.
Our fluent interfaces are going to guide you (with support from your IDE) through building queries.
But it's not all, thanks to libpg_query we were able to create a postgresql parser that covers 100% of syntax since it's literally extracted from the server code 🤯 (full support up to PostgreSQL 17)
Why do we need a parser?
\- query analysis (security but also static analysis)
\- we can programmatically access/modify queries - like for example add advanced pagination
And if non of this sounds appealing, thanks to parser and deparser flow-php/postgresql comes also with query formatter - just like php-cs-fixer or mago formatter but for sql queries!
On top of that we also created Client interface with a default implementation based on ext-pgsql that comes with a support for Row Mappers (an interface). Our plan is to provide bridges for libraries like cuyz/valinor or crell/serde that will let us make queries results strictly typed through:
$client->fetchInto(User::class, "SELECT * FROM users WHERE id = $2, [10001\]);
You can find library documentation here: https://flow-php.com/documentation/components/libs/postgresql/
It's still early development, not battle tested yet, feedback/bug reports/ideas are greatly appreciated and welcome 😊
https://redd.it/1po87go
@r_php
Hey everyone!
I would like to share our recent addition to Flow PHP framework, a brand new PostgreSQL library based on ext-pgsql and pganalyze/libpg_query
Doctrine DBAL is awesome! But since it's database engine agnostic, it's missing some nice features like for example, query builder is not covering all db specific features like CTE.
This makes us to either keep SQL queries as plain strings, or make some tradeoffs while using Query Builder, flow-php/postgresql covers this gap providing probably the most advanced query builder in PHP.
Our fluent interfaces are going to guide you (with support from your IDE) through building queries.
But it's not all, thanks to libpg_query we were able to create a postgresql parser that covers 100% of syntax since it's literally extracted from the server code 🤯 (full support up to PostgreSQL 17)
Why do we need a parser?
\- query analysis (security but also static analysis)
\- we can programmatically access/modify queries - like for example add advanced pagination
And if non of this sounds appealing, thanks to parser and deparser flow-php/postgresql comes also with query formatter - just like php-cs-fixer or mago formatter but for sql queries!
On top of that we also created Client interface with a default implementation based on ext-pgsql that comes with a support for Row Mappers (an interface). Our plan is to provide bridges for libraries like cuyz/valinor or crell/serde that will let us make queries results strictly typed through:
$client->fetchInto(User::class, "SELECT * FROM users WHERE id = $2, [10001\]);
You can find library documentation here: https://flow-php.com/documentation/components/libs/postgresql/
It's still early development, not battle tested yet, feedback/bug reports/ideas are greatly appreciated and welcome 😊
https://redd.it/1po87go
@r_php
Flow-Php
Documentation - Flow PHP - Data Processing Framework
WSL2 development environment for PHP projects with little to no fuss
PHP is great, but setting up a truly functional development environment is a pain. There are so many moving parts I sometimes feel I'm wasting more time on the environment than on coding.
I remember using XAMPP back in the day - when it was still the go-to solution. Somebody should tell them that PHP 8.3 was released. And PHP 8.4. Even 8.5. Get with the program...
So I started reading about a WSL development environment which seems to hit the right marks:
An environment that matches the production one closely. This prevents surprises when I release my code.
Full freedom to set up what I need, when I need it. Sometimes too much freedom.
A virtual machine sandbox that is separate from my main system. I don't have to worry about stuff escaping the virtual machine and deleting my games... I mean my totally-legit, work-related stuff.
I can pick my preferred Linux distribution, which makes it a breeze to change versions for each component. No more uninstalls and reinstalls every time I'm switching projects.
But that freedom thing I mentioned above is the one that worries me. A WSL recipe with Ansible provides the fix. It sets everything up: PHP, Apache, MariaDB, Git, Composer, PhpMyAdmin. Then I can start coding, maybe add some vhosts along the way.
The big part of the setup is covered in this article.
What do you guys use for your development envoronments?
https://redd.it/1povij7
@r_php
PHP is great, but setting up a truly functional development environment is a pain. There are so many moving parts I sometimes feel I'm wasting more time on the environment than on coding.
I remember using XAMPP back in the day - when it was still the go-to solution. Somebody should tell them that PHP 8.3 was released. And PHP 8.4. Even 8.5. Get with the program...
So I started reading about a WSL development environment which seems to hit the right marks:
An environment that matches the production one closely. This prevents surprises when I release my code.
Full freedom to set up what I need, when I need it. Sometimes too much freedom.
A virtual machine sandbox that is separate from my main system. I don't have to worry about stuff escaping the virtual machine and deleting my games... I mean my totally-legit, work-related stuff.
I can pick my preferred Linux distribution, which makes it a breeze to change versions for each component. No more uninstalls and reinstalls every time I'm switching projects.
But that freedom thing I mentioned above is the one that worries me. A WSL recipe with Ansible provides the fix. It sets everything up: PHP, Apache, MariaDB, Git, Composer, PhpMyAdmin. Then I can start coding, maybe add some vhosts along the way.
The big part of the setup is covered in this article.
What do you guys use for your development envoronments?
https://redd.it/1povij7
@r_php
docs.dotkernel.org
Setup Packages - development - Dotkernel Documentation
Development Environment using AlmaLinux
How we lit up 1200 screens in real time at SymfonyCon
https://symfony.com/blog/how-we-lit-up-1200-screens-in-real-time-at-symfonycon?utm_medium=feed&utm_source=Symfony%20Blog%20Feed
https://redd.it/1pox1th
@r_php
https://symfony.com/blog/how-we-lit-up-1200-screens-in-real-time-at-symfonycon?utm_medium=feed&utm_source=Symfony%20Blog%20Feed
https://redd.it/1pox1th
@r_php
Symfony
How we lit up 1200 screens in real time at SymfonyCon (Symfony Blog)
At SymfonyCon 2025, we wanted to celebrate Symfony’s 20th anniversary with a live, collective experience: 1200 developers holding up their phones while we lit up their screens in real time from the …
Free Source Code: part 1
https://youtu.be/4EuaQrDcSFk?si=CffI-ztoW9OfKSgv
https://redd.it/1pp1nu0
@r_php
https://youtu.be/4EuaQrDcSFk?si=CffI-ztoW9OfKSgv
https://redd.it/1pp1nu0
@r_php
My Message to Laravel TEAM
Concern About Laravel’s Direction & Request for Stable, Bootstrap-Friendly Alternatives
My Message to Laravel TEAM
I’ve been a passionate Laravel developer for nearly a decade. Laravel’s early alignment with Bootstrap via
However, with recent shifts—especially the strong push toward Tailwind CSS, Inertia, Livewire, and ecosystem monetization (e.g., Forge, Vapor, paid packages)—I’m finding it increasingly difficult to stay aligned with Laravel’s direction.
As someone who values simplicity, stability, and proven stacks (PHP + Blade + Bootstrap), I feel the framework is drifting away from developers like me—the ones who helped grow Laravel organically in its early years—toward a more opinionated, JavaScript-heavy, and commercialized approach.
The deprecation of
I’m now seriously considering alternatives:
CodeIgniter 4 is tempting (I loved v3), but I’m unsure if its ecosystem is mature enough for larger applications today.
Are there other stable, well-documented PHP frameworks that prioritize convention over configuration, support clean MVC, and make it easy to use Blade (or plain PHP) with Bootstrap—without forcing frontend tooling or paid add-ons?
I’m not resistant to change—but I am resistant to churn without clear, inclusive justification. Laravel used to excel at balancing innovation with stability. I hope it finds that balance again.
Thank you for listening.
https://redd.it/1pp0y1n
@r_php
Concern About Laravel’s Direction & Request for Stable, Bootstrap-Friendly Alternatives
My Message to Laravel TEAM
I’ve been a passionate Laravel developer for nearly a decade. Laravel’s early alignment with Bootstrap via
laravel/ui played a huge role in my adoption—and advocacy—of the framework. Over the years, I’ve shipped numerous projects and actively recommended Laravel to peers and teams.However, with recent shifts—especially the strong push toward Tailwind CSS, Inertia, Livewire, and ecosystem monetization (e.g., Forge, Vapor, paid packages)—I’m finding it increasingly difficult to stay aligned with Laravel’s direction.
As someone who values simplicity, stability, and proven stacks (PHP + Blade + Bootstrap), I feel the framework is drifting away from developers like me—the ones who helped grow Laravel organically in its early years—toward a more opinionated, JavaScript-heavy, and commercialized approach.
The deprecation of
laravel/ui and the focus on Breeze/Breeze + Inertia have made starting new projects with my preferred stack unnecessarily complex. Laravel 12, in particular, feels like a departure from the philosophy and ergonomics I fell in love with in Laravel 5–11.I’m now seriously considering alternatives:
CodeIgniter 4 is tempting (I loved v3), but I’m unsure if its ecosystem is mature enough for larger applications today.
Are there other stable, well-documented PHP frameworks that prioritize convention over configuration, support clean MVC, and make it easy to use Blade (or plain PHP) with Bootstrap—without forcing frontend tooling or paid add-ons?
I’m not resistant to change—but I am resistant to churn without clear, inclusive justification. Laravel used to excel at balancing innovation with stability. I hope it finds that balance again.
Thank you for listening.
https://redd.it/1pp0y1n
@r_php
Reddit
From the PHP community on Reddit
Explore this post and more from the PHP community
Inertia best practice
I’m mainly backend dev and worked for years with frontend/backend communicating through an API layer.
Now I have an Inertia project where I often feel like that I’m working against the framework. I have some concerns where I want to know what the best practice way of handling such scenarios is.
1. Dealing with large Datasets
I have multiple pages where I have a lot of data that gets transmitted to Frontend. The docs don’t give much info about this but what’s the best way of dealing with this. Especially on subsequent data reloads (ie after form submission or router.reload). I know I can provide the ‘only’ parameter but that still has to run the controller function and thus, all the other code not necessarily required for that few requested parameters. The only current solution I see would be a closure. But this doesn’t feel very “finished” as it forces a lot of duplicate code and overall makes the code look ugly.
2. Dynamic requests
Let’s say there is some button that the user can interact with that triggers something beyond CRUD. Currently in the codebase these are done with plain axios requests. But those completely ignore the Inertia ecosystem. I feel like that’s kind of the wrong approach of doing it. The controllers on the backend side are therefore mixed with inertia and json responses.
3. Error handling
This is currently all over the place. Inertia has a beautiful way of displaying errors. Because dynamic requests aren’t within the ecosystem, it doesn’t apply to those requests. I have my own complete approach of correcting this but I wanted to hear if there is maybe already a best-practice way of doing this. This is also a general Laravel concern. Coming from Spring, everything error related is done through exceptions. Does that fit for Laravel too?
https://redd.it/1pp412t
@r_php
I’m mainly backend dev and worked for years with frontend/backend communicating through an API layer.
Now I have an Inertia project where I often feel like that I’m working against the framework. I have some concerns where I want to know what the best practice way of handling such scenarios is.
1. Dealing with large Datasets
I have multiple pages where I have a lot of data that gets transmitted to Frontend. The docs don’t give much info about this but what’s the best way of dealing with this. Especially on subsequent data reloads (ie after form submission or router.reload). I know I can provide the ‘only’ parameter but that still has to run the controller function and thus, all the other code not necessarily required for that few requested parameters. The only current solution I see would be a closure. But this doesn’t feel very “finished” as it forces a lot of duplicate code and overall makes the code look ugly.
2. Dynamic requests
Let’s say there is some button that the user can interact with that triggers something beyond CRUD. Currently in the codebase these are done with plain axios requests. But those completely ignore the Inertia ecosystem. I feel like that’s kind of the wrong approach of doing it. The controllers on the backend side are therefore mixed with inertia and json responses.
3. Error handling
This is currently all over the place. Inertia has a beautiful way of displaying errors. Because dynamic requests aren’t within the ecosystem, it doesn’t apply to those requests. I have my own complete approach of correcting this but I wanted to hear if there is maybe already a best-practice way of doing this. This is also a general Laravel concern. Coming from Spring, everything error related is done through exceptions. Does that fit for Laravel too?
https://redd.it/1pp412t
@r_php
Reddit
From the laravel community on Reddit
Explore this post and more from the laravel community
New SymfonyCasts Course: Bundle Development
https://symfony.com/blog/new-symfonycasts-course-bundle-development?utm_medium=feed&utm_source=Symfony%20Blog%20Feed
https://redd.it/1pp4oxb
@r_php
https://symfony.com/blog/new-symfonycasts-course-bundle-development?utm_medium=feed&utm_source=Symfony%20Blog%20Feed
https://redd.it/1pp4oxb
@r_php
Symfony
New SymfonyCasts Course: Bundle Development (Symfony Blog)
Ever wondered what makes a great Symfony bundle? This new SymfonyCasts course takes you from an empty directory to a production-ready bundle that feels right at home in the Symfony ecosystem.
Simulating Сoncurrent Requests: How We Achieved High-Performance HTTP in PHP Without Threads
https://medium.com/manychat-engineering/simulating-%D1%81oncurrent-requests-how-we-achieved-high-performance-http-in-php-without-threads-c3a94bae6c3b
https://redd.it/1ppnwtf
@r_php
https://medium.com/manychat-engineering/simulating-%D1%81oncurrent-requests-how-we-achieved-high-performance-http-in-php-without-threads-c3a94bae6c3b
https://redd.it/1ppnwtf
@r_php
Medium
Simulating Сoncurrent Requests: How We Achieved High-Performance HTTP in PHP Without Threads
A behind-the-scenes look at the async tricks and serialization hacks that helped us push PHP far beyond its limits.
Claude Code plugin Symfony ! Superpowers
🚀 New Claude Code Plugin: superpowers-symfony 🚀
Hey everyone! I just published a new Claude Code plugin for Symfony developers: superpowers-symfony — a plugin that brings Symfony-specific guidance, skills, and workflows straight into Claude! GitHub
📦 Features include:
✔️ TDD workflows using Pest or PHPUnit
✔️ Doctrine ORM mastery (relations, migrations, fixtures)
✔️ API Platform patterns & DTO guidance
✔️ Symfony Messenger async support
✔️ Security best practices & voters
✔️ Architecture patterns (hexagonal, DI, CQRS)
✔️ Quality tooling (PHP-CS-Fixer, PHPStan, etc.)
✔️ Docker + Symfony support (FrankenPHP & standard compose) GitHub
💡 What it does:
This plugin adds a collection of expert-level skills that Claude can use to help with common Symfony tasks — from writing tests to building APIs and structuring apps.
Give it a try and let me know what you think! 🙌
https://redd.it/1pppbiz
@r_php
🚀 New Claude Code Plugin: superpowers-symfony 🚀
Hey everyone! I just published a new Claude Code plugin for Symfony developers: superpowers-symfony — a plugin that brings Symfony-specific guidance, skills, and workflows straight into Claude! GitHub
📦 Features include:
✔️ TDD workflows using Pest or PHPUnit
✔️ Doctrine ORM mastery (relations, migrations, fixtures)
✔️ API Platform patterns & DTO guidance
✔️ Symfony Messenger async support
✔️ Security best practices & voters
✔️ Architecture patterns (hexagonal, DI, CQRS)
✔️ Quality tooling (PHP-CS-Fixer, PHPStan, etc.)
✔️ Docker + Symfony support (FrankenPHP & standard compose) GitHub
💡 What it does:
This plugin adds a collection of expert-level skills that Claude can use to help with common Symfony tasks — from writing tests to building APIs and structuring apps.
Give it a try and let me know what you think! 🙌
https://redd.it/1pppbiz
@r_php
GitHub
GitHub - MakFly/superpowers-symfony
Contribute to MakFly/superpowers-symfony development by creating an account on GitHub.
20 Years of Symfony in Code Stats
https://symfony.com/blog/20-years-of-symfony-in-code-stats?utm_medium=feed&utm_source=Symfony%20Blog%20Feed
https://redd.it/1pprbsj
@r_php
https://symfony.com/blog/20-years-of-symfony-in-code-stats?utm_medium=feed&utm_source=Symfony%20Blog%20Feed
https://redd.it/1pprbsj
@r_php
Symfony
20 Years of Symfony in Code Stats (Symfony Blog)
A look at 20 years of Symfony through code statistics, revealing how contributions, complexity, and long-term design choices shaped the framework.
How realistic is it to freelance part-time as an aspiring software developer?
Hi everyone,
I’m an aspiring software developer (currently training as a Fachinformatiker Application Development) and I’m thinking about doing small freelance jobs on the side (just a few hours per week). How realistic are my chances with my current skill level, and what would be good first steps to get real clients?
What I can currently do / offer (small, clearly scoped tasks):
Plain PHP + MySQL: bug fixes, small features, CRUD, forms, validation
SQL: fixing/optimizing queries, simple database structures
Basic JavaScript: small fixes (events, buttons, form logic)
I’ve already created profiles on a few platforms like Fiverr or Malt. I’m not sure whether linking profiles is allowed here, so I’ll only share them if explicitly requested.
https://redd.it/1ppq0xk
@r_php
Hi everyone,
I’m an aspiring software developer (currently training as a Fachinformatiker Application Development) and I’m thinking about doing small freelance jobs on the side (just a few hours per week). How realistic are my chances with my current skill level, and what would be good first steps to get real clients?
What I can currently do / offer (small, clearly scoped tasks):
Plain PHP + MySQL: bug fixes, small features, CRUD, forms, validation
SQL: fixing/optimizing queries, simple database structures
Basic JavaScript: small fixes (events, buttons, form logic)
I’ve already created profiles on a few platforms like Fiverr or Malt. I’m not sure whether linking profiles is allowed here, so I’ll only share them if explicitly requested.
https://redd.it/1ppq0xk
@r_php
Reddit
From the PHP community on Reddit
Explore this post and more from the PHP community
Laravel Reverb - Real-time communication built-in
https://youtu.be/Sfy1cpaEPaw
https://redd.it/1ppxlb9
@r_php
https://youtu.be/Sfy1cpaEPaw
https://redd.it/1ppxlb9
@r_php
YouTube
Reverb - Real-time communication built-in
Laravel Reverb is a blazing-fast, scalable WebSocket server for Laravel. Add real-time communication to your application with
first-party broadcasting support. No third-party services required.
➡️ Learn more
https://laravel.com/docs/12.x/broadcasting
➡️…
first-party broadcasting support. No third-party services required.
➡️ Learn more
https://laravel.com/docs/12.x/broadcasting
➡️…
Free source code: Part 2
https://youtu.be/71LjTzL53fk?si=x_zUJepPid3e8J0K
https://redd.it/1pq0afu
@r_php
https://youtu.be/71LjTzL53fk?si=x_zUJepPid3e8J0K
https://redd.it/1pq0afu
@r_php
Small PHP + SQLite web app for managing custom ZIP-based file formats
I’m sharing a small PHP project that manages a custom ZIP-based file format ( .broccoli ) via a web UI.
Tech stack:
PHP (no framework)
SQLite
ZipArchive
Self-hosted, file-based workflows
Repo: https://github.com/crispilly/brassica
Use case: managing Broccoli recipe files in the browser.
Happy to hear feedback on structure or security aspects.
https://redd.it/1pqfmz4
@r_php
I’m sharing a small PHP project that manages a custom ZIP-based file format ( .broccoli ) via a web UI.
Tech stack:
PHP (no framework)
SQLite
ZipArchive
Self-hosted, file-based workflows
Repo: https://github.com/crispilly/brassica
Use case: managing Broccoli recipe files in the browser.
Happy to hear feedback on structure or security aspects.
https://redd.it/1pqfmz4
@r_php
GitHub
GitHub - crispilly/brassica: WebApp zur Verwaltung und Bearbeitung von Rezepten im .broccoli-Format. Kompatibel mit der Broccoli…
WebApp zur Verwaltung und Bearbeitung von Rezepten im .broccoli-Format. Kompatibel mit der Broccoli-App. - crispilly/brassica
Pitch Your Project 🐘
In this monthly thread you can share whatever code or projects you're working on, ask for reviews, get people's input and general thoughts, … anything goes as long as it's PHP related.
Let's make this a place where people are encouraged to share their work, and where we can learn from each other 😁
Link to the previous edition: /u/brendt_gd should provide a link
https://redd.it/1pqgieq
@r_php
In this monthly thread you can share whatever code or projects you're working on, ask for reviews, get people's input and general thoughts, … anything goes as long as it's PHP related.
Let's make this a place where people are encouraged to share their work, and where we can learn from each other 😁
Link to the previous edition: /u/brendt_gd should provide a link
https://redd.it/1pqgieq
@r_php
Reddit
From the PHP community on Reddit
Explore this post and more from the PHP community
I wrote a thing... wanna help me break it?
https://github.com/ssnepenthe/symbol-extractor
You give it a file path as input and it gives you back a list of classes, enums, functions, interfaces, and traits declared within that file as output.
It's pretty simple but PHP can be weird so I am sure there are edge cases I am missing.
Is anyone willing to take some time to try to come up with examples of valid PHP that breaks it?
https://redd.it/1pqocta
@r_php
https://github.com/ssnepenthe/symbol-extractor
You give it a file path as input and it gives you back a list of classes, enums, functions, interfaces, and traits declared within that file as output.
It's pretty simple but PHP can be weird so I am sure there are edge cases I am missing.
Is anyone willing to take some time to try to come up with examples of valid PHP that breaks it?
https://redd.it/1pqocta
@r_php
GitHub
GitHub - ssnepenthe/symbol-extractor
Contribute to ssnepenthe/symbol-extractor development by creating an account on GitHub.
A backoffice for people who don’t use Laravel (yes, we still exist)
I’m experimenting with a framework-free PHP backoffice/admin tool I built and would love some feedback from the community.
I mainly work on custom PHP projects, especially platforms for managing clinical and research data. In these contexts, adopting a full-stack framework like Laravel or Symfony isn’t always practical.
Over time, I often found myself building backoffices and admin interfaces from scratch, so I started experimenting with a small, framework-free solution of my own.
The main goal was long-term readability: PHP code that I can easily understand and modify even months later. Defining tables and edit forms should take just a few lines, while keeping the control flow explicit and easy to follow.
For the same reason, I made deliberately conservative technical choices: plain PHP, Bootstrap for layout, no template engine, and no JavaScript dependencies. In my experience, stacking frameworks, template engines, and JS libraries makes long-term maintenance harder, especially for small or regulated projects.
Conceptually, it’s inspired by tools like Filament, but simpler, less ambitious, and without Laravel behind it. It’s not meant to compete with Laravel, WordPress, or anything similar. The project is still in alpha, so no guarantees regarding stability or completeness.
I’m curious whether this kind of approach still makes sense in today’s PHP ecosystem. I’ve shared the code (MIT) and a short write-up explaining the design choices. Feedback is welcome, including critical opinions.
If anyone’s curious, here are the link:
https://github.com/giuliopanda/milk-admin
https://redd.it/1pqpq9r
@r_php
I’m experimenting with a framework-free PHP backoffice/admin tool I built and would love some feedback from the community.
I mainly work on custom PHP projects, especially platforms for managing clinical and research data. In these contexts, adopting a full-stack framework like Laravel or Symfony isn’t always practical.
Over time, I often found myself building backoffices and admin interfaces from scratch, so I started experimenting with a small, framework-free solution of my own.
The main goal was long-term readability: PHP code that I can easily understand and modify even months later. Defining tables and edit forms should take just a few lines, while keeping the control flow explicit and easy to follow.
For the same reason, I made deliberately conservative technical choices: plain PHP, Bootstrap for layout, no template engine, and no JavaScript dependencies. In my experience, stacking frameworks, template engines, and JS libraries makes long-term maintenance harder, especially for small or regulated projects.
Conceptually, it’s inspired by tools like Filament, but simpler, less ambitious, and without Laravel behind it. It’s not meant to compete with Laravel, WordPress, or anything similar. The project is still in alpha, so no guarantees regarding stability or completeness.
I’m curious whether this kind of approach still makes sense in today’s PHP ecosystem. I’ve shared the code (MIT) and a short write-up explaining the design choices. Feedback is welcome, including critical opinions.
If anyone’s curious, here are the link:
https://github.com/giuliopanda/milk-admin
https://redd.it/1pqpq9r
@r_php
GitHub
GitHub - giuliopanda/milk-admin: MILK ADMIN - Build your PHP application from a ready-made base.
MILK ADMIN - Build your PHP application from a ready-made base. - giuliopanda/milk-admin
Mago 1.0.0: The Rust-based PHP Toolchain is now Stable (Linter, Static Analyzer, Formatter & Architectural Guard)
Hi r/PHP!
After months of betas (and thanks to many of you here who tested them), I am thrilled to announce **Mago 1.0.0**.
For those who missed the earlier posts: Mago is a unified PHP toolchain written in **Rust**. It combines a Linter, Formatter, and Static Analyzer into a single binary.
**Why Mago?**
1. **Speed:** Because it's built in Rust, it is significantly faster than traditional PHP-based tools. ([See the benchmark](https://mago.carthage.software/benchmarks)).
2. **Unified:** One configuration (`mago.toml`), one binary, and no extensions required.
3. **Zero-Config:** It comes with sensible defaults for linting and formatting (PER-CS) so you can start immediately.
**New in 1.0: Architectural Guard**
We just introduced **Guard**, a feature to enforce architectural boundaries. You can define layers in your `mago.toml` (e.g., `Domain` cannot depend on `Infrastructure`) and Mago will enforce these rules during analysis. It’s like having an architecture test built directly into your linter.
**Quick Start**
You can grab the binary directly or use Composer:
```bash
# Via Composer
composer require --dev carthage-software/mago
# Or direct install (Mac/Linux)
curl --proto '=https' --tlsv1.2 -sSf https://carthage.software/mago.sh | bash
```
**Links**
* **GitHub:** https://github.com/carthage-software/mago
* **Documentation:** https://mago.carthage.software
* **Playground:** https://mago.carthage.software/playground
A huge thank you to the giants like PHPStan and Psalm for paving the way for static analysis in PHP. Mago is our take on pushing performance to the next level.
I'd love to hear what you think!
https://redd.it/1pr1725
@r_php
Hi r/PHP!
After months of betas (and thanks to many of you here who tested them), I am thrilled to announce **Mago 1.0.0**.
For those who missed the earlier posts: Mago is a unified PHP toolchain written in **Rust**. It combines a Linter, Formatter, and Static Analyzer into a single binary.
**Why Mago?**
1. **Speed:** Because it's built in Rust, it is significantly faster than traditional PHP-based tools. ([See the benchmark](https://mago.carthage.software/benchmarks)).
2. **Unified:** One configuration (`mago.toml`), one binary, and no extensions required.
3. **Zero-Config:** It comes with sensible defaults for linting and formatting (PER-CS) so you can start immediately.
**New in 1.0: Architectural Guard**
We just introduced **Guard**, a feature to enforce architectural boundaries. You can define layers in your `mago.toml` (e.g., `Domain` cannot depend on `Infrastructure`) and Mago will enforce these rules during analysis. It’s like having an architecture test built directly into your linter.
**Quick Start**
You can grab the binary directly or use Composer:
```bash
# Via Composer
composer require --dev carthage-software/mago
# Or direct install (Mac/Linux)
curl --proto '=https' --tlsv1.2 -sSf https://carthage.software/mago.sh | bash
```
**Links**
* **GitHub:** https://github.com/carthage-software/mago
* **Documentation:** https://mago.carthage.software
* **Playground:** https://mago.carthage.software/playground
A huge thank you to the giants like PHPStan and Psalm for paving the way for static analysis in PHP. Mago is our take on pushing performance to the next level.
I'd love to hear what you think!
https://redd.it/1pr1725
@r_php
mago.carthage.software
The Oxidized PHP Toolchain: Blazing fast linter, formatter, and static analyzer for PHP, written in Rust.