PHP - BlogFlock

Removing a filename containing a null byte or binary character on Linux - Blog entries :: mwop.net

2026-02-06T17:01:27.000Z

Somehow, I got a file in my tree that started with a null byte. I only discovered it because git status was noting it wasn't added to my branch, and wanted to know if I wanted to add it.

No, no, I did not. I wanted to delete it.

But, of course, you cannot reference such a file by name, so I had to learn a few tricks.

First off, you can list names with binary bytes using:

/bin/ls -lb

But even better, you can get the inode if you use:

/bin/ls -li

When you do, the inode is in the first column of the list for each file.

Once you know that, you can delete the file, using find:

find . -maxdepth 1 -inum <inode_id> -exec rm -i -- {} +

Removing a filename containing a null byte or binary character on Linux was originally published 6 February 2026 on https://mwop.net by Matthew Weier O'Phinney.

Dad - Rob Allen

2026-01-22T15:00:00.000Z

I don't often post personal things here, however last weekend my dad died peacefully in his sleep and it feels important to acknowledge this.

I have no words.

2025 in pictures - Rob Allen

2025-12-31T17:52:04.000Z

As we reach the end of 2025, I take this opportunity to look back over the photos that I have taken and thing about the year. This year I published 1,064 photos to Flickr with, of course, at least one photo every day as part of my Project 365.

The lovely thing is that my photos remind me what happened during my year and I remember many good times through them as I've seen friends and family over the months. I've done for many years now and you can see them all in my Year in pictures category.

January

I started the year visiting the Severn Valley Railway and took some photos of steam trains. I also visited PHP Stoke which was fun.

February

I attended three community events in February, starting with FOSDEM at the very start, PHP UK mid-way through, and then Fusion towards the end. I really like catching up with the community and learning from them in the hallway track! I also photographed planes with Stuart!

March

I had a quick trip to Spain this month which was very cold and wet and then spoke at Drupal Mountain Camp; my first time attending this conference and I loved the community vibe here. I was also enjoyed my visit to the KVWR with Kevin.

April

In April, I went down to London to take care of my dad while my mum visited her sister in America. I fitted in a trip to the SVR Spring Gala, and also spoke at PHP Berkshire, sharing the bill with Dave Liddament

May

We celebrated lots of birthdays in May and visited Dudley Canal & Caverns. I spoke at phpday in Verona and later the PHP Oxford user group. The community at both events are fantastic and I enjoyed all the great conversations. My wife and I also enjoyed a visit to Charlecote. Most importantly, Crystal Palace won the FA cup this month for the first time in their history!

June

The Nintendo Switch 2 was released this month and it's a great sequel to the original Switch. We spent most of the month on holiday in Spain, where I ate lots of ice cream.

July

July was all about family and friends. My aunt and cousins from America visited, so we moved our family meet-up to July. We also had our regular lunch with friends in Crewe as that's half-way between us. We also celebrated our youngest's graduation of a first class degree in mathematics.

August

There was a big railway event in August celebrating 200 years of the modern railways. I visited mum & dad and I took dad out for breakfast at the local café which turned out to be the last time that dad and I will do that. We also visited our friend in Estonia.

September

The big news in September is that my dad's wellbeing deteriorated far enough that mum was no longer able to care for him. He was taken to hospital and is now living in a care home. I'm pleased that the transition seems to have gone smoothly for both of them. Later that month, I attended apidays London and then took a few days to take photos of trains in Yorkshire, while catching up with good friends in the evenings. The Moors really are a lovely place to spend time.

October

In October, my aunt from America visited again which was lovely as she stayed with my mum, arriving a few days after dad had moved into a care home. I also spoke at Nordic APIs Platform Summit in Stockholm. I was surprised to be on the main track and the conference as a whole was excellent. Finally, we celebrated another graduation as my wife graduated with a first class degree in Computing.

November

A quiet month, where I spoke at SymfonyCon which celebrated the 20th anniversary of the framework.

December

I finished the year attending apidays Paris, my first visit to this very large conference, where I met some amazing people and learned things. We had a lovely Christmas at home where lots of cake and mince pies were consumed. Then, right at the end of the month, I visited the SVR for the final time this year to take photos of heritage diesel locomotives. I also bought a new camera for next year!

Looking back over 2025, it was a bittersweet year with some excellent times with family, friends and community folks, but it was tinged with my dad's transition to a care home. As always, I also very much enjoyed my railway photography and trips with Stuart.

Who knows what 2026 will bring, but I will continue to take photos throughout!

Built-in Laravel Support: A New Era for PhpStorm Developers - PhpStorm : The IDE that empowers PHP developers | The JetBrains Blog

2025-12-10T17:02:10.000Z

For years, PhpStorm has been the go-to IDE for PHP developers – powerful and deeply integrated with the language. But there was one thing many kept asking for: Laravel support out of the box.

It should come with built-in
— Amdadul Haq (@amdad121) July 30, 2025

Starting with PhpStorm 2025.3, Laravel support is now built in. From the moment you open your project, everything just works – no plugins, no configuration, no extra steps.

Discover the story behind this update from PhpStorm Team Lead Roman Pronskiy, PhpStorm Software Developer Maria Filippova, JetBrains Product Lead Artemy Pestretsov, Laravel Idea plugin creator Adel Faizrakhmanov, Laravel creator Taylor Otwell, and JetBrains Developer Advocate for PHP Brent Roose:

Start your Laravel journey

FAQ

I use IntelliJ IDEA. How is Laravel support provided there?

In IntelliJ IDEA, you can install the Laravel Idea plugin as usual from the main menu: File | Settings | Plugins | Marketplace → “Laravel Idea”.

Will the standalone Laravel Idea plugin continue to be maintained?

Yes. Adel and the PhpStorm team will continue collaborating to ensure the plugin – and PhpStorm’s integrated support – remain the top-tier Laravel development experience in the industry.

Is Laravel support available if I’m using PhpStorm for free?

Yes. The built-in Laravel support is available to all PhpStorm users, including those using:

The 30-day free trial.
Early access builds.
Free licenses, such as licenses for students, teachers, open-source projects, or startups.

If you can run PhpStorm, you can use Laravel support – no limitations.

I use PhpStorm. Can I now uninstall the Laravel Idea plugin?

In PhpStorm, the Laravel Idea plugin now comes pre-installed and enabled, so you no longer have to download or manage it manually. However, you should keep the plugin enabled; disabling or removing it will turn off all Laravel-specific features.

From zsh to fish - Blog entries :: mwop.net

2025-11-17T23:00:10.000Z

I'm a longtime zsh user. A colleague introduced me to it in 2009, and I was an instant convert, if nothing else than for directory aliases and simpler $PATH management. Within a couple of years, I discovered oh-my-zsh, which put my shell on steroids, giving me a ton of completion capabilities, better prompts, and more.

But a few years ago, I started noticing that my shell load times were getting worse and worse. At that time, I discovered I could easily switch to vanilla zsh with zplug managing a small number of plugins I used (nvm, fzf, and a few others). I also discovered starship, which gave me more prompt options, with faster startup times.

And yet...

I kept reading Julia Evans recommending fish. She often would note that fish just does things that other shells need plugins or customization for: decent tab completion, better history capabilities, etc.

So I took the plunge finally in the past couple weeks to give fish a try.

Configuration

First off, the switch more than halved the amount of configuration I needed to have an equivalent setup. I was able to remove a ton of configuration I had in zsh around history management, autocompletion, and overrides.

As I noted, with zsh, I was using zplug, and I had a half-dozen plugins. With fish, initially I had no plugins, but in order to get nvm running, I needed to install fisher, the de facto fish plugin manager. But that's literally the only plugin I'm now using.

I continued to use starship and fzf, which meant two lines of configuration in my fish configuration, and no changes otherwise.

And there's no lag whatsoever when starting up a shell. With zsh, even with my minimal config, I would sometimes wait a second or two for a shell to spawn. With fish, no wait.

Discoveries

One thing I've kept from oh-my-zsh is a utility called take, which does the following:

If given a directory name, it creates it, and then enters it
If given an archive file, it unarchives it into a directory, and then enters that directory
If given a git repository name, it clones it, and then enters that directory

When porting this to fish, I discovered some really cool features of that shell.

First, fish will automatically autoload functions from the functions/ subdirectory of your fish configuration. So if you name the function the same as the file (e.g., functions/take.fish), it will load it on demand. This is a nice performance improvement over loading everything.

Second, fish uses a standard syntax for any block statement. Instead of sometimes needing braces, sometimes needing a keyword (which generally varies BASED on the block type - e.g. fi to end a conditional, done to end a loop), all blocks use an end keyword. This makes it far simpler to remember and less prone to errors.

Third, when defining a function, you can specify variable names to which to capture arguments. This is far easier to visually parse and use than standard posix shells, where you use positional parameters. As an example:

function takedir -a newpath
    mkdir -p $newpath && cd $newpath
end

Fourth, while you can use the notation varname=value to define variables, there's a better built-in, the set directive, which can:

Define block-local (set -l) and function-local (set -f) variables
Define globally-available variables (set -g)
Define environment variables (set -x, for export) that persist to child shells

Using this, it's far easier both to ensure that a variable is scoped correctly, as well as to reason about the scope of a given variable. And those captured arguments I mentioned? Automatically scoped to the function, so they won't bleed outside of it.

(There's also a "univeral" flag, -u, which will not only set it in the current shell, at the globally available level, but make it available across any other instances, and persist it for future invocations. This seems dangerous, though!)

The combination of these meant that the take declaration took fewer lines of code, was easier to understand, and less likely to bleed state. I'll take it!

But will I stick with it?

I think so. I even put it on some servers I maintain, and it's instantly given me more and better functionality than the default shell available on each, which makes being on those servers more comfortable. Having less configuration is something I've been keeping an eye on, as more configuration means it's harder to reason about how things work, and more likely to break or fail in interesting ways when updating or upgrading.

I'll still need to keep my bash chops; provisioning scripts for containers and VMs generally have to depend on this lowest common denominator. However, having a useful out-of-the-box shell for my workstation and servers that's easy to script? I'll take it.

From zsh to fish was originally published 17 November 2025 on https://mwop.net by Matthew Weier O'Phinney.

IPTC export changed in Photos for macOS 26 Tahoe - Rob Allen

2025-11-11T11:00:00.000Z

I've recently upgraded my MacBook Air to macOS 26 Tahoe and one thing I noticed was that Rodeo's rules were no longer working. With the help of exiftool, I worked out that when exporting to JPEG from Photos for macOS 26 Tahoe, the Object Name, Caption-Abstract and Keywords IPRC properties were no longer being populated. This is a regression from macOS 15 Sequoia.

This is the data from exiftool.

Output from macOS 15 Sequoia:

$ exiftool -f -ObjectName -Caption-Abstract -Keywords IMG_8016.jpeg
Object Name                     : Replaced the broken nose pad on my glasses
Caption-Abstract                : It's a nuisance when the nosepad breaks!
Keywords                        : glasses, Project 365, 365:2025

Output from macOS 26.1:

$ exiftool -f -ObjectName -Caption-Abstract -Keywords IMG_8016.jpeg
Object Name                     : -
Caption-Abstract                : -
Keywords                        : -

This is obviously, less than helpful if your application reads these fields!

Fortunately, the export from macOS 26 Tahoe does fill in some other fields with this data: Title, Description and Subject. These ones are populated by both macOS 15 and 26:

Output from macOS 15 Sequoia:

$ exiftool -f -Title -Description -Subject IMG_8016.jpeg
Title                           : Replaced the broken nose pad on my glasses
Description                     : It's a nuisance when the nosepad breaks!
Subject                         : glasses, Project 365, 365:2025

Output from macOS 26.1:

$ exiftool -f -Title -Description -Subject IMG_8016.jpeg
Title                           : Replaced the broken nose pad on my glasses
Description                     : It's a nuisance when the nosepad breaks!
Subject                         : glasses, Project 365, 365:2025

I checked the IPTC reference images and they populate Object Name, Caption-Abstract and Keyword in the same way as macOS 15 Sequoia does, so I'm at a loss as to why this is broken in the new macOS 26.

Regardless, I have updated Rodeo appropriately, and version 0.5 resolves this problem!

PhpStorm Plugins You Might Not Know - PhpStorm : The IDE that empowers PHP developers | The JetBrains Blog

2025-11-04T16:15:49.000Z

PhpStorm comes with a ton of built-in features, and you can add even more with plugins. They bring new languages, tools, and small improvements that make everyday coding smoother.

Many of the best ones come from independent developers. One of them is Dmitrii Derepko, who built several handy tools for working with web projects and PHP. Below are a few of his creations worth checking out.

If you’re curious about plugin development, don’t miss the JetBrains Plugin Developer Conference 2025 – free online conference. Dmitrii will be speaking there and will walk you through plugin creation basics: from the initial setup to releasing it on JetBrains Marketplace.

.gitattributes support

If you’ve ever worked with libraries distributed through Composer, NPM, or other package managers, you’ve probably seen a .gitattributes file. It controls how your project looks when archived (via git archive) and which files get included or excluded when users install your package.

The .gitattributes Support plugin adds first-class editing experience for this file in PhpStorm. It highlights syntax, recognizes attribute rules, and even suggests valid options while you type so you don’t have to look them up each time. Small details, but they make editing smoother and help prevent mistakes.

🔗 Plugin Marketplace
💻 Source on GitHub

Git Codeowners

If you use GitHub or GitLab, you’ve probably seen a CODEOWNERS file. It tells your platform who’s responsible for reviewing pull requests that touch specific parts of the codebase.

The Git CODEOWNERS plugin makes editing this file painless. It autocompletes file paths, suggests team names, and validates syntax to prevent mistakes before you commit.

🔗 Plugin Marketplace
💻 Source on GitHub

Cron / Crontab Support

Cron is the classic tool for running tasks on a schedule. But remembering its five-field syntax is… painful.

This plugin highlights errors in your cron expressions, translates them into plain English (“runs every Monday at 3 AM”), and even lets you execute commands directly from PhpStorm – no need to switch to the terminal.

🔗 Plugin Marketplace
💻 Source on GitHub

Sitemap Support

Sitemaps tell search engines which URLs your site exposes and when they were last updated.

This plugin gives you a table-like XML editor for editing and inspecting sitemap files. You can view indexed vs. non-indexed pages, search or filter entries, and tweak URLs by hand if your generator misses something.

🔗 Plugin Marketplace
💻 Source on GitHub

TempestPHP

A work-in-progress plugin that adds support for Tempest (an upcoming new PHP framework) to PhpStorm. Features include support for its custom view syntax, route- and view file support, autocompletion for database models, and more.

🔗 Plugin Marketplace
💻 Source code on GitHub

Buggregator

Buggregator is a visual debugging toolkit that lets you inspect data dumps right inside PhpStorm.

Just call trap() in your PHP code, and the plugin automatically spins up a local server that listens for these calls and renders the data in a docked panel — no browser tabs, no context switching.

It also works seamlessly with the libraries you already use, like Ray, Symfony/VarDumper, Monolog, Sentry, etc.

🔗 Plugin Marketplace
💻 Source on GitHub

PHP Dump

PHP Dump builds on PHP Opcodes Language to visualize your code’s compiled output in real time.

It tokenizes the current file, shows the AST (Abstract Syntax Tree), and displays Opcache details. It helps you understand why a specific function might run slower than expected, without ever executing it.

🔗 Plugin Marketplace
💻 Source on GitHub

FileSystem Info

Sometimes you just want to know which files in your project are taking up space or sitting forgotten.

FileSystem Info scans your project tree and adds file sizes in the project structure tree so you can quickly spot large files.

🔗 Plugin Marketplace
💻 Source on GitHub

Git Churn

Git Churn shows you which files in your repository change too often or never change at all.

Frequent edits usually signal overly complex or unstable code. This plugin helps you spot those hotspots so you can refactor with purpose instead of guesswork.

🔗 Plugin Marketplace
💻 Source on GitHub

That’s it for this roundup – a few plugins that make PhpStorm just a bit smarter.

If you ever had an idea for a PhpStorm plugin or run into something that could be automated or improved, drop it in the comments – maybe Dmitrii (or someone else from the community) will take it on next!

CSS Feature Selectors - Blog entries :: mwop.net

2025-11-03T20:09:00.000Z

I have a number of locations on my website where I've been faking a masonry layout (you know, like how Pinterest lays things out) using CSS grid columns. They work, but they're not what I'm looking for.

I've been waiting for the official masonry grid display to land, and discovered that it's now an experimental feature in Chrome-based browsers that you can enable (it's been available for Firefox for awhile).

But... how can I check to see if the feature exists? Turns out CSS already has that covered, via the @supports selector:

@supports (display: masonry) {
    .container {
        display: masonry;
    }
}

@supports not (display: masonry) {
    .container {
        display: grid;
    }
}

I love that CSS is fully embracing the idea of progressive enhancement! I've used feature testing in JS for a long while, but hadn't realized this was now baked in to CSS, too.

CSS Feature Selectors was originally published 3 November 2025 on https://mwop.net by Matthew Weier O'Phinney.

Linux desktop files and xdg-open - Blog entries :: mwop.net

2025-11-03T19:39:35.000Z

I've been using Linux on the desktop for more than 25 years now. While I don't put icons on my desktop any longer (and haven't for probably around 15 years), I do use the gnome-shell launcher to quickly open programs, and this utilizes desktop files.

Recently, I wanted to create launchers for different Obsidian vaults. Obsidian provides a URL schema for this: obsidian://open?vault=VaultName. The application registers the schema handler with the system, so this should open, but evidently you can no longer use "Type=Link" in your desktop files.

What I found:

You MUST have a "Version=1.0" line; gnome-shell just ignored any of my desktop files that omitted it.
You can use xdg-open in your Exec line to open the URL.

[Desktop Entry]
Version=1.0
Name=Notes
Icon=/usr/share/icons/hicolor/256x256/apps/obsidian.png
Comment=My Obsidian vault for notes
Categories=Office;ProjectManagement;
Type=Application
Exec=xdg-open "obsidian://open?vault=notes"

Linux desktop files and xdg-open was originally published 3 November 2025 on https://mwop.net by Matthew Weier O'Phinney.

The State of PHP 2025 - PhpStorm : The IDE that empowers PHP developers | The JetBrains Blog

2025-10-15T14:00:04.000Z

The State of PHP 2025 examines how developers use, prefer, and rely on PHP, showing how this long-standing web language continues to modernize through new frameworks, improved tooling, and AI-assisted workflows.

In this report, we present findings from the Developer Ecosystem Survey 2025. Alongside the numbers, you’ll also hear commentary from Brent Roose, JetBrains Developer Advocate for PHP, and insights from other community experts explaining what’s shaping PHP today and where the ecosystem is heading.

If you’d like to see what the ecosystem looked like just a year ago, check out the State of PHP 2024.

Participants

This year, we collected responses from 1,720 developers who indicated PHP as their main programming language, with the largest populations living in Japan, the United States, Russia, China, and France.

88% of PHP developers have more than three years of experience, with the largest single group falling in the six-to-ten-year range.

Team size and work environment

More than half of PHP developers (56%) work in small teams of two to seven people, while 12% work independently.

Language adoption and usage

The majority of PHP developers (58%) do not plan to migrate to other languages in the next year. For those who do, Go and Python are the most attractive alternatives.

The share of newcomers is slowly growing: 4% have been using PHP for less than six months (up from 2% last year), and 6% for less than one year. Still, almost three-quarters (72%) of developers report over four years of PHP usage, underlining the ecosystem’s maturity.

“Important to note is that these numbers aren’t talking about people leaving PHP – they are about adopting languages besides PHP. I think it’s great to see so many PHP developers who are adding other languages to their toolbelt. PHP has areas where it shines, but there are also problems that are better solved with languages like Go or Rust. Working together across those language barriers leads to great results.”

Brent Roose JetBrains Developer Advocate for PHP

“It’s great to see more newcomers in PHP. It’s not surprising given the amount of positive buzz around PHP for the past couple of years, but it’s nice to see the numbers proving this trend as well.”

Brent Roose JetBrains Developer Advocate for PHP

The trend toward modernization continues: PHP 8.x dominates with 89% usage, while PHP 7.x has dropped to 33%. Legacy versions (5.6 and earlier) are now down to 8%, though not entirely gone. Read Brent’s blog post for a more in-depth analysis of PHP versions’ usage.

“I think the open-source community plays a vital role in pushing the PHP community forward to adopt more secure and performant versions. The best part is that by using tools like Rector, upgrading becomes almost trivial. I speak from experience: The yearly upgrade is so well worth it.”

Brent Roose JetBrains Developer Advocate for PHP

PHP frameworks and CMSs

No major shifts occurred in framework adoption: Laravel continues to lead with 64% usage, followed by WordPress (25%) and Symfony (23%). Other frameworks like CodeIgniter, Yii, and CakePHP hold smaller but stable shares.

“We’re thrilled to see Laravel adoption continuing to grow, driven by innovations like Laravel Cloud and AI integrations such as Laravel Boost and MCP. Laravel remains focused on providing a comprehensive, modern full-stack solution that makes PHP development more productive and accessible than ever.”

Taylor Otwell Creator of Laravel

“Symfony contributors continue to push the boundaries of what can be expressed through type annotations, creating a virtuous cycle where codebases, static analyzers, and IDEs continuously improve to enhance developer experience and verifiability. Informal communication channels between all stakeholders make this progress even smoother and more efficient.”

Nicolas Grekas Core Developer at Symfony

PHP development environments

Most used IDE or editor

One of the most striking changes is in tooling: The share of those using either PhpStorm or IntelliJ IDEA with the PHP plugin has gone up by 10 percentage points, to 68%. Visual Studio Code’s share has dropped to 23%, while new players like Cursor (6%) have also entered the scene.

Satisfaction with coding tools

We also asked PHP developers how satisfied they are with their primary IDE. Among them, 53% of PhpStorm users gave their IDE the highest possible rating, compared to just 26% of VS Code users.

IDE or editor of choice per framework

PhpStorm dominates in Symfony (83%) and leads in Laravel (62%), while WordPress developers remain more split, with VS Code remaining a popular choice (37%).

Did you know Laravel support is now free for all PhpStorm users? This blog post has the full story.

Debugging and testing

When it comes to debugging, most developers still rely on var_dump-style approaches (59%), though debugger adoption (e.g. Xdebug) has risen slightly to 39%.

“Xdebug’s usage seems to be pretty stable throughout the years and across several surveys: between 30% and 35%. While I definitely still do my fair share of “dd” or “log” debugging, there are times where having a debugger at hand and knowing how to use it saves so much time. It’s a skill that takes practicing and doesn’t come overnight – which is why I made this short video to help folks get started with Xdebug.”

Brent Roose JetBrains Developer Advocate for PHP

PHPUnit (50%) remains the standard, but Pest adoption has gained four percentage points to reach 17%, showing momentum toward modern, developer-friendly testing frameworks.

“I’m super-happy to see more and more people choosing Pest as their go-to testing framework – the growth in this year’s survey really reflects the quality of our recent releases.

Since the survey, we’ve actually released Pest 4, which introduces test sharding, profanity checking, and the revolutionary browser testing. Having proper browser testing in the PHP world is truly a game-changer, so I expect adoption to increase even more next year!”

Nuno Maduro Creator of Pest

However, 32% of developers still don’t write tests at all, which highlights a persistent gap in testing culture.

Code quality tools

The clear winner in 2025 is PHPStan, which jumped to 36% usage, up nine percentage points from last year. Tools like PHP CS Fixer (30%) and PHP_CodeSniffer (22%) remain widely used, while Rector (10%) continues its steady rise. Still, 42% of respondents don’t use any code quality tools regularly, leaving room for further improvement.

💡Have you tried JetBrains Qodana? This static analysis and codebase auditing tool brings inspections from PhpStorm into your CI/CD pipeline, along with unique and custom code-quality and security checks. Use it to clean up and secure your team’s code before merging to the main branch.

Adoption of AI

AI has gone mainstream: 95% of developers have tried at least one AI tool, and 80% regularly use AI assistants or AI-powered editors.

ChatGPT leads daily use with 49%, though its share has dropped since 2024. GitHub Copilot (29%) and JetBrains AI Assistant (20%) follow, with the latter tripling its adoption since last year.

“AI is here to stay. It’s great to see the increased adoption of AI overall, and the drop in ChatGPT usage in favor of more specialized tooling. We can expect more of this moving forward, with new tools entering the scene, and the ones giving us the best boost earning their place in our daily stack.”

Ashley Hindle AI Engineer at Laravel

Looking ahead, 72% of respondents are likely to try AI coding agents in the next year, while only 8% say it’s unlikely.

To support developers in this shift, earlier this year JetBrains introduced an AI coding agent called Junie. Unlike other coding assistants, Junie is built to work directly with your JetBrains IDE, project context, and team practices, delivering actionable and trustworthy support. With AI agents rapidly becoming part of everyday workflows, Junie brings the reliability, integration, and developer focus you expect from JetBrains to this new wave of tools.

At the same time, not every company is ready to embrace AI yet. 11% respondents report that their organization is unlikely to try AI coding agents in the next 12 months. Apart from the data privacy and security concerns (44%) and intellectual property questions (24%), many companies also struggle with a lack of knowledge about such tools (22%).

Ecosystem highlights 2025

FrankenPHP

“One of my personal highlights in PHP this year is FrankenPHP becoming a project backed by the PHP Foundation. I think there’s a lot of potential for the project to become the de-facto standard runtime for PHP, which would be huge. FrankenPHP has a lot of performance optimizations that work out of the box for any PHP application, it’s portable across systems, and it has worker mode, which allows for asynchronous request handling in PHP, which can speed up applications by a factor of three compared to using PHP FPM.”

Brent Roose JetBrains Developer Advocate for PHP

Learn more about FrankenPHP from Kévin Dunglas on PHPverse 2025:

PHPverse

This year also marked a special milestone – PHP turned 30 years old. We celebrated with JetBrains PHPverse, an online birthday event that drew more than 26,000 viewers worldwide. If you missed it, don’t worry – the recordings are available to watch on demand:

Catch the next edition of PHPverse – sign up here to be the first to know when registration opens.

Get event updates

What this means for PHP

The 2025 results confirm that PHP remains a stable, professional, and evolving ecosystem. Its strong developer base, continued dominance of Laravel and WordPress, increasing adoption of modern tooling, and rapid embrace of AI-powered workflows show that PHP is far from being “legacy”.

Disclaimer: Despite all the measures we’ve taken to secure a representative pool of respondents, these results might be slightly skewed toward users of JetBrains products, as they might have been more likely to take the survey. Read more about our methodology.

Appending text to Obsidan via Shortcuts - Rob Allen

2025-10-14T10:00:00.000Z

Sometimes it's helpful to add some text to my current Obsidian daily note without having to switch to Obsidian, find the daily note and then type my text.

To do this, we can use the magic of Obsidian's obsidian:// URI schema and automate the text capture in Apple Shortcuts, with an assigned keyboard shortcut to activate it.

This is the Shortcut:

There's a number of steps in the Shortcut. Firstly we Ask For some text which will display a dialog box for us to type in. Then we Replace any trailing whitespace, add then use a Text action to prepend the current time as a third level heading. This is the text to be added, so we URL Encode it and use another Text action to create the full obsidian:// URI to be Opened.

The URI is:

obsidian://daily?vault=General&append=1&content={URL Encoded Text}

The daily endpoint only works if the Daily notes core plugin is enabled. We then need to specify which vault we're using. The content is the URL encoded text to be appended and the append parameter tells obsidian to place the text at the end of the note.

I've assigned it to ⌃⌥⌘= and pressing that key combination runs it for me.

Now I have a simple way to add some text to the current note without interrupting my context.

If this shortcut would be useful to you, you can download it here.

mac-volume: A CLI to control device volume - Rob Allen

2025-10-07T10:00:00.000Z

I've set my Mac up such that video calls such as Zoom use the microphone and earphones attached to my Behringer UMC204HD, which all other audio plays through the my normal speakers which are the default.

One issue I have with this is that it's quite hard to change the volume when a call as the volume buttons on the Mac are connected to the default output. This finally annoyed me enough that I looked into how to control the volume of a device and wrote a little command line utility for this, so that I could attach it to buttons on my StreamDeck using Keyboard Maestro.

Changing the volume

The way to control the volume on a Mac programmatically is to use Core Audio, specifically AudioObjectSetPropertyData(). This function takes a deviceID and some other properties, including volume. The deviceID is of type AudioDeviceID and the volume is a floating point number between 0 and 1.

It's not easy to remember device IDs, so I decided to use the device name instead and map the volume to between 0 and 100. This makes it easy to say set the volume to 10%:

mac-volume "MacBook Pro Speakers" set 10

To get the list of device names, I wrote a list-devices command. The list is available from AudioObjectGetPropertyData() which returns list of AudioDeviceID items. The name is in the kAudioObjectPropertyName selector, so that's easy enough.

The main trouble is that CoreAudio is a C API and so dealing with it from Swift involves use of references and UnsafeMutablePointer which is a bit hairy as it's been a while since I've had to worry about pointers!

Increment and decrement

While you can get the current volume, add to it and then set to increase the volume, it's easier to let the app do it, so mac-volume also supports incrementing and decrementing by an amount. These are the two command that I bind to StreamDeck keys.

I found that a step size of 3 was a good choice for raising/lowering the volume with a reasonable number of presses of the key.

It's on GitHub

If you need to control the volume of a non-default audio device from the command line, mac-volume is on GitHub at akrabat/mac-volume.

Moving PHP open source forward - PhpStorm : The IDE that empowers PHP developers | The JetBrains Blog

2025-10-02T09:10:34.000Z

At JetBrains, we want the PHP community to shine. First and foremost, we do this by building PhpStorm, the best IDE for PHP development; but we also support and help drive the PHP Foundation; have just organised PHPverse, accessible for everyone worldwide; and recently we made the Laravel Idea plugin free for all.

On top of that, we support open-source projects that we believe impact the PHP community or have the potential to do so, and which will benefit from our financial support.

Our support includes free PhpStorm licenses for active open source maintainers, but also financial sponsorships. With this blog post, we’d like to announce a new round of sponsorships, as well as a more structured approach towards new open source sponsorships in the future.

Sponsorships 2025-2026

Our strategy from now on is to sponsor around five open-source projects and maintainers per year. Each year we’ll select new projects to diversify our support.

Here are the people we’ll sponsor for the coming year:

Saif Eddin Gmati, who’s building a very promising new linter and static analyzer for PHP in Rust: Mago.
Markus Staab, who’s involved in tons of existing open-source projects like PHPStan, Rector, and PHPUnit.
Kyrian Obikwelu, who’s actively exploring AI and MCP possibilities in PHP.
Sjon Hortensius, who’s responsible for 3v4l.org, an online shell for PHP that’s very popular within the PHP community.

You may have noticed there’s still one spot open. Maybe you know just the right person or project to add to this list? Feel free to reach out to brent.roose@jetbrains.com with your suggestions, or leave a comment below this blog post!

Apart from sponsoring individual projects, we also stay committed to sponsoring the PHP Foundation, and encourage as many organizations to do so as well.

Sponsor PHP Foundation

Finally, because of this new yearly system, we also stopped sponsoring two projects we’ve supported for many years. Not because we don’t believe in them anymore, but because we want to make sure we can support as many different projects as possible over time. Maybe this is a good time to take a look if you or your company can pick up new sponsorships as well?

Derick Rethans, who’s working on Xdebug
Juliette Reinders Folmer, who’s working on CodeSniffer

We believe in the power of open-source. We want to support it and encourage you to do the same if you have the means to do so.

Let’s work together to make PHP even better!

Opening Slack Jira Cloud links in the right browser - Rob Allen

2025-09-30T10:00:00.000Z

I use OpenIn to open links in a given browser when I click on them in other applications. This is really helpful to keep various work related stuff in different browsers or profiles and I find it very helpful.

One thing that's bothered me is that links from the Jira Cloud Slack App ignore my OpenIn rules and always open in Safari and I finally sat down to work out why.

The investigation

I create a new OpenIn rule and enabled multiple browsers so that OpenIn would present a choice window to me.

It looks like this

At the bottom, we can see the link that OpenIn has received.

Even though the presented URL in the Slack app is https://my-client.atlassian.net/browser/PROJ-123, and if you right click and copy link, that's what you get in your clipboard, when you click on the link, you get a slack.com link.

Copying that link, it's of the form: https://slack.com/openid/connect/login_initiate_redirect?login_hint=eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.blah.blah.

That's interesting! I've seen that eyJhbGci prefix often enough to know on sight that it's the start of base64 encoded JWT and sure enough, base64 decoding it proved that it was.

The format of JWT is {header}.{payload}.{signature} and it's unencrypted, so we can inspect the payload easily enough. This is redacted, but it's of the form:

{
  "aud" : "123456789.123456789",
  "auth_time" : 1758615553,
  "exp" : 1758619153,
  "https://slack.com/target_uri" : "https://{my-client}.atlassian.net/browse/PROJ-123",
  "https://slack.com/team_id" : "ABCDEFGHI",
  "https://slack.com/user_id" : "U01AB2CDEF3",
  "iat" : 1758615553,
  "iss" : "https://slack.com",
  "sub" : "rob@{my-client}.com"
}

We can see that the URL that we want to go to is in the payload's "https://slack.com/target_uri" property, so we just need to set up OpenIn to use that URL and pick the appropriate browser.

OpenIn's custom scripts

One really nice feature of OpenIn is that you can write custom scripts for a rule, so we can use this to extract the payload and pick the browser.

So I read the web page and wrote some Javascript!

The work we need to do is:

Extract the payload from the query parameter
JSON decode it
Read the target_uri
Choose browser based on target_uri

This needs a few helper functions

Helper functions

Extracting the payload is straightforward JS. We need the text between the two .s:

function extractJwtPayload(str) {
    const parts = str.split('.');
    return parts.length >= 3 ? parts[1] : '';
}

As OpenIn uses WebKit's JavaScriptCore, we can decode base64 using Uint8Array.fromBase64():

function base64Decode(str) {
    const uint8Array = Uint8Array.fromBase64(str);
    return String.fromCharCode(...uint8Array);
}

We also need to select the browser that we want the link to open in. This is done in OpenIn by setting all the "visible" browsers to false, except the one you want:

function selectBrowser(browser) {
    let apps = ctx.getApps()
    apps.forEach(function (app) {
        app.visible = (app.name == browser)
    })
}

Do the work

Having set everything up, we can now find the target_uri and choose the browser.

Firstly we only want to do this work if the source app is Slack and that we have a login_hint parameter:

if (ctx.getSourceApp().path.startsWith("/Applications/Slack.app") 
    && ctx.url.searchParams.has('login_hint')) {

Extracting the target_uri is a case of using the functions we've written:

const login_hint = ctx.url.searchParams.get('login_hint');
const jwtPayload = extractJwtPayload(login_hint);
const payload = base64Decode(jwtPayload).replace(/\0/g, '');
const data = JSON.parse(payload);
const target_uri = data['https://slack.com/target_uri'];

Note that I discovered some null bytes during testing, so removed them from the decoded string.

Now we set OpenIn's URI and select the browser we want:

// Set OpenIn's URL
ctx.url.href=target_uri;

// Select the browser
if (target_uri.includes("my-client-1")) {
    selectBrowser("Firefox");
    return;
}

if (target_uri.includes("my-client-2")) {
    selectBrowser("Firefox");
    return;
}

// Default to Safari
selectBrowser("Safari");
return;

and we're done.

That's it

That's it! Whenever I click on a Jira link in Slack, the correct browser opens directly to where I want to go.

The full script is here: openin-slack-app-link.js

Disabling the Zoom mini window on Linux - Blog entries :: mwop.net

2025-09-23T14:20:27.000Z

Zoom used to have a strange behavior, one I'm sure they thought would be useful, but in reality was infuriating: if you moved between virtual workspaces, Zoom would minimize to a thumbnail window that followed you around to workspaces.

At some point, it went away, thankfully... but after a recent release, it turned back on, and it's been a huge pain for me. There's a bug in that the mini window follows me to the initial virtual workspace, but then doesn't follow around from there, requiring me to use the workspace tools to move it to the workspace I want, and then re-maximize it, only to have to do the whole thing again if I switch screens.

The solution turns out to be relatively simple, if incredibly unintuitive.

Zoom does NOT have a GUI setting for this, for some reason. But evidently it creates the file $HOME/.config/zoomus.conf, which is where all configuration is stored.

This file is in INI format. Find the entry enableMiniWindow, and set it to false:

enableMiniWindow=false

Restart Zoom, and you're set.

Disabling the Zoom mini window on Linux was originally published 23 September 2025 on https://mwop.net by Matthew Weier O'Phinney.

Fixing PostgreSQL collation version mismatch - Rob Allen

2025-09-23T10:00:00.000Z

After pulling a new version of the Docker PostgreSQL container, I started getting this warning:

WARNING:  database "dev" has a collation version mismatch
DETAIL:  The database was created using collation version 2.36, but the operating system provides version 2.41.
HINT:  Rebuild all objects in this database that use the default collation and run ALTER DATABASE dev REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.

This seems to have occurred because the underlying OS was changed to Trixie from Bullseye for the default image. i.e. I used:

image: postgres:17

Rather than:

image: postgres:17-bookworm

This is on my dev machine, so it's not a major problem as usually I can just blow away the database and recreate it. However, I have some test data that I don't want to lose quite yet, so I took a backup using pg_dump and then did this instead:

REINDEX DATABASE dev;
ALTER DATABASE dev REFRESH COLLATION VERSION;

The warning's now gone.

Of course, in production, you'll want to be a bit more careful and a pg_dump and load is more likely to avoid any risks of corruption. As ever, YMMV.

Jumping to the end of bash's history - Rob Allen

2025-09-16T10:00:00.000Z

I use bash's history all the time, via ctrl+r and also with the up and down keys; it's wonderful.

Sometimes, I want to get back to the end of my history and I recently discovered that there's a shortcut for this: meta+>. It doesn't matter where you are in your history, pressing meta+> jumps you to the end and you have a blank prompt again.

I use iTerm2 on my Mac and have my right hand option key set to meta. This is done in Settings→Profiles→Keys, setting "Right Option (C) key:" to "Esc+".

However, to press meta+>, I need to do right-option+shift+. which isn't as easy as right-option+., so let's rebind!

To rebind, I looked up the bash command for this functionality (`end-of-history`), and then added this to my .bashrc:

bind '"\e.": end-of-history'

All done. Now I just press right-option+. and I'm back at the end of history as if I'd never navigated it.

Understanding All Relations Between Classes, Interfaces, Traits, and Enums in PHP - Exakat

2025-09-15T20:29:11.000Z

Understanding Relationships Between Classes, Interfaces, Traits, and Enums in PHP

Modern PHP offers four major code structures — classes, interfaces, traits, and enums — each with its own purpose and rules. But the real power of PHP comes from how these structures can interact with each other. This page gathers all relations between classes in PHP.

If you’ve ever wondered “Can an enum use a trait?” or “Can a trait implement an interface?”, the answer lies in PHP’s keywords: extends, implements, and use. These keywords define the legal relationships between the building blocks of your code.

To make this crystal clear, here’s a matrix showing who can interact with whom — and with which keyword.

Can interact with…	class	interface	trait	enum
class	extends one class(single inheritance); Or composition	extends one or multiple interface	use one or multiple traits	Cannot extend an enum (no inheritance), can only call its cases
interface	Cannot extend a class	extends one or multiple interfaces	Cannot use a trait	Cannot implement or extend an enum
trait	Cannot extend a class	Cannot implement an interface	useother traitsinside a trait	Cannot use an enum
enum	Cannot extend a class	implementsone or multiple interfaces	use one or multiple traits	Cannot extend another enum

Key Takeaways

Classes are the most versatile: they can extend a class, implement interfaces, and use traits.
Interfaces can only extend other interfaces — nothing else.
Traits are like reusable code fragments. They can be used in classes and enums and even use other traits, but cannot stand alone.
Enums (introduced in PHP 8.1) behave like special classes: they cannot extend other classes or enums, but they can implement interfaces and use traits.

The post Understanding All Relations Between Classes, Interfaces, Traits, and Enums in PHP appeared first on Exakat.

Converting JWKS JSON to PEM using Python - Rob Allen

2025-09-09T10:00:00.000Z

Following on from my earlier exploration of JWKS (RFC7517), I found myself needing to convert the JWKS into PEM format.

This time I turned to Python with my preference of using uv with inline script metadata and created jwks-to-pem.py.

The really nice thing about inline script metadata is that we can use the cryptography package to do all the hard work with RSA and serialisation. We just have to remember that the base64 encoded values are base64 URL encoded and account for it.

As a single file python script, I make it executable with chmod +x jwks-to-pem.py and made it so that I can pipe the output of a curl call to it, or pass in a JSON file. I prefer to use the curl solution though with:

curl -s https://example.com/.well-known/jwks.json | jwks-to-pem.py

Example

Here's an example from the University of Cambridge.

On the day I wrote this article, the JWKS looks like this:

$ curl -s https://api.apps.cam.ac.uk/oauth2/v1/.well-known/jwks.json
{
  "keys": [
    {
      "alg": "RS256",
      "e": "AQAB",
      "n": "6kKjjctVPalX0ypJ2irwog8xIXS9JTABqrSnK_n3YJ4q0aH2-1bjGbWz8p1CaCUqDxQSDuqzvOgMdNGvZrxlNJ-G8hfc39jrb_KnB0T3ZsuxFz6X0mDzmHhdiPjSDK3M0syC4qg5_PB7xwKail5VWOcY0SypIYCPD6Ct5DGnQ_XONGXIVG7eaJAHdxJp2BOz0n3BVEFnZUgM5JcfGrSFfGqb0ZotX2AblwjZKQc58E0EVVykJw8gxW1Bob8rbaVXlMHssfY-9Jx0zua7ZrjO5C4OMmt9J6zYbVnGVwf62ehGtcLSP6iCG4_XM2sAMQwqJnPBss0U9WwDERk17FMHvb_FBwxAFxRygd0DclWmQmCYr5uFYck57KGARtyoxrNNAf4AFUHuObjbV24TyInYEgMhKi3SAML_4ke3dbbG-mjchXPN9OqNd4fydnQIP39WFHmFNk_nIlqvYnALI4xPE-w09T9jCvjU8hYHHlVMRvRluBnUzJkFnxLse5W-agC6ITe3wYvKH7SHVp6MYQWVD_0I2rCLV4gqjSpXzKIMs5eejjTQQq0VYumgL_f1ETvzDoewzXLOC8GGu2LZDwDbP0ea6DchReWjZfj4nJx23uQyGAj1h_uPI1jCd9oeJhbN8jFz2ltYgXYBp51qdSzsbtdec9BPPBVeXjI--c0AWU8",
      "kid": "70e0ed3c",
      "kty": "RSA",
      "use": "sig"
    }
  ]
}

They very kindly pretty-print it too!

We can then get the PEM version by piping to jwks-to-pem.py:

$ curl -s https://api.apps.cam.ac.uk/oauth2/v1/.well-known/jwks.json | jwks-to-pem.py
# Key 0 (kid: 70e0ed3c)
-----BEGIN PUBLIC KEY-----
MIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEA6kKjjctVPalX0ypJ2irw
og8xIXS9JTABqrSnK/n3YJ4q0aH2+1bjGbWz8p1CaCUqDxQSDuqzvOgMdNGvZrxl
NJ+G8hfc39jrb/KnB0T3ZsuxFz6X0mDzmHhdiPjSDK3M0syC4qg5/PB7xwKail5V
WOcY0SypIYCPD6Ct5DGnQ/XONGXIVG7eaJAHdxJp2BOz0n3BVEFnZUgM5JcfGrSF
fGqb0ZotX2AblwjZKQc58E0EVVykJw8gxW1Bob8rbaVXlMHssfY+9Jx0zua7ZrjO
5C4OMmt9J6zYbVnGVwf62ehGtcLSP6iCG4/XM2sAMQwqJnPBss0U9WwDERk17FMH
vb/FBwxAFxRygd0DclWmQmCYr5uFYck57KGARtyoxrNNAf4AFUHuObjbV24TyInY
EgMhKi3SAML/4ke3dbbG+mjchXPN9OqNd4fydnQIP39WFHmFNk/nIlqvYnALI4xP
E+w09T9jCvjU8hYHHlVMRvRluBnUzJkFnxLse5W+agC6ITe3wYvKH7SHVp6MYQWV
D/0I2rCLV4gqjSpXzKIMs5eejjTQQq0VYumgL/f1ETvzDoewzXLOC8GGu2LZDwDb
P0ea6DchReWjZfj4nJx23uQyGAj1h/uPI1jCd9oeJhbN8jFz2ltYgXYBp51qdSzs
btdec9BPPBVeXjI++c0AWU8CAwEAAQ==
-----END PUBLIC KEY-----

The script

This is the script in case anyone else finds it useful:

#!/usr/bin/env -S uv run --script --quiet
# /// script
# dependencies = [
#   "cryptography",
# ]
# ///

"""Convert JWK keys to PEM format.

This script reads .well-known/jwks.json and outputs PEM encoded versions
of the public keys in that file.

Usage:
    curl -s https://example.com/.well-known/jwks.json | jwks-to-pem.py
    uv run jwks-to-pem.py jwks.json
    uv run jwks-to-pem.py < jwks.json

Requirements:
    - uv (https://github.com/astral-sh/uv)
    - cryptography library

Author:
    Rob Allen 
    Copyright 2025

License:
    MIT License - https://opensource.org/licenses/MIT
"""

import json
import base64
import sys
from cryptography.hazmat.primitives import serialization
from cryptography.hazmat.primitives.asymmetric import rsa

def base64url_decode(data):
    """Decode base64url to bytes"""
    # Add padding if needed
    padding = 4 - len(data) % 4
    if padding != 4:
        data += '=' * padding

    # Replace URL-safe chars
    data = data.replace('-', '+').replace('_', '/')

    # Decode
    return base64.b64decode(data)

def jwk_to_pem(jwk_key):
    """Convert JWK to PEM format"""
    if jwk_key['kty'] != 'RSA':
        raise ValueError("Only RSA keys are supported")

    # Decode the modulus (n) and exponent (e) to int
    n = int.from_bytes(base64url_decode(jwk_key['n']), 'big')
    e = int.from_bytes(base64url_decode(jwk_key['e']), 'big')

    # Create RSA public key
    public_key = rsa.RSAPublicNumbers(e, n).public_key()

    # Serialize to PEM
    pem = public_key.public_bytes(
        encoding=serialization.Encoding.PEM,
        format=serialization.PublicFormat.SubjectPublicKeyInfo
    )
    return pem.decode()

def main():
    if len(sys.argv) > 2:
        print("Usage: jwk_to_pem.py [jwks.json]")
        print("If no file is provided, reads from stdin")
        sys.exit(1)

    if len(sys.argv) == 2 and sys.argv[1] != '-':
        # Read from file
        with open(sys.argv[1], 'r') as f:
            jwks = json.load(f)
    else:
        # Read from stdin
        jwks = json.load(sys.stdin)

    # Convert each key
    for i, key in enumerate(jwks['keys']):
        kid = key.get('kid', f'key-{i}')
        print(f"# Key {i} (kid: {kid})")
        print(jwk_to_pem(key))

if __name__ == "__main__":
    main()

Connect MCP Servers to Junie in PhpStorm - PhpStorm : The IDE that empowers PHP developers | The JetBrains Blog

2025-09-05T14:47:16.000Z

The Model Context Protocol (MCP) is an open standard introduced by Anthropic. Think of it as a USB-C port for AI: a consistent way to plug the AI models your AI agent uses into specific tools and data sources.

You can connect Junie, the AI coding agent by JetBrains, to a wide variety of officially provided or community built MCP servers, or build your own MCP server using one of the available SDKs – including the brand-new MCP PHP SDK.

About MCP PHP SDK

MCP SDKs are lightweight frameworks that handle the protocol details so that developers can focus on the application functionality that AI agents will use.

MCP PHP SDK is the official MCP SDK built as a joint effort by the PHP Foundation, Anthropic’s MCP team, and Symfony. The goal of the project is to provide a framework-agnostic, production-ready reference implementation the PHP ecosystem can rely on. For details about using MCP PHP SDK or contributing to it, see modelcontextprotocol/php-sdk.

Junie + MCP

Whether you are building your own MCP server or using an existing one, here’s how to make it work with the Junie AI agent in PhpStorm:

Make sure that the MCP server can be accessed and started.
The specific way of starting an MCP server depends on this server’s implementation – please refer to the MCP server documentation for instructions.
Configure Junie in PhpStorm to connect.
To add the MCP server to Junie, press ⇧Shift twice to open the search window and search for “MCP Settings”. On the MCP Settings page, you can see the list of connected servers and add or edit JSON configurations for the MCP servers in the ~/.junie/mcp.json file.

To configure an MCP server at the project level, manually add an mcp.json file with your desired server configurations to the .junie/mcp folder in the project root.

To view the list of actions that Junie can perform through a configured MCP server, locate the server in the MCP Settings list and expand the Status drop-down list.

For example, with the Laravel Boost MCP server, Junie gets useful tools for working with Laravel projects, such as listing Artisan commands, routes, or config files, reading logs, querying the database, or searching versioned documentation.

This is where MCP shines: It bridges the gap between LLMs and dynamic, framework- and project-specific context and data.
Start using new commands and context inside your IDE.
When running a prompt, Junie analyzes what commands registered with the configured MCP servers are relevant, and executes them through the respective MCP server.

The Junie coding agent keeps evolving. Join the conversation in our Junie Discord community and help shape what’s next for Junie.

New chapter for MCP servers in PHP

While you could use any SDK implementation to create MCP servers for PHP projects, the official MCP PHP SDK boosts the contribution of the PHP community into the AI ecosystem, both within the PHP realm and beyond.

The PHP SDK maintainers encourage PHP developers to submit their MCP integrations for PHP frameworks and tools – Laravel, Symfony, WordPress, custom APIs, and more – to be listed in the SDK GitHub repo.

PHP - BlogFlock

Removing a filename containing a null byte or binary character on Linux - Blog entries :: mwop.net

Dad - Rob Allen

2025 in pictures - Rob Allen

January

February

March

April

May

June

July

August

September

October

November

December

Built-in Laravel Support: A New Era for PhpStorm Developers - PhpStorm : The IDE that empowers PHP developers | The JetBrains Blog

FAQ

I use IntelliJ IDEA. How is Laravel support provided there?

Will the standalone Laravel Idea plugin continue to be maintained?

Is Laravel support available if I’m using PhpStorm for free?

I use PhpStorm. Can I now uninstall the Laravel Idea plugin?

From zsh to fish - Blog entries :: mwop.net

Configuration

Discoveries

But will I stick with it?

IPTC export changed in Photos for macOS 26 Tahoe - Rob Allen

PhpStorm Plugins You Might Not Know - PhpStorm : The IDE that empowers PHP developers | The JetBrains Blog

.​gitattributes support

Git Codeowners

Cron / Crontab Support

Sitemap Support

TempestPHP

Buggregator

PHP Dump

FileSystem Info

Git Churn

CSS Feature Selectors - Blog entries :: mwop.net

Linux desktop files and xdg-open - Blog entries :: mwop.net

The State of PHP 2025 - PhpStorm : The IDE that empowers PHP developers | The JetBrains Blog

Participants

Team size and work environment

Language adoption and usage

PHP frameworks and CMSs

PHP development environments

Most used IDE or editor

Satisfaction with coding tools

IDE or editor of choice per framework

Debugging and testing

Code quality tools

Adoption of AI

Ecosystem highlights 2025

FrankenPHP

PHPverse

What this means for PHP

Appending text to Obsidan via Shortcuts - Rob Allen

mac-volume: A CLI to control device volume - Rob Allen

Changing the volume

Increment and decrement

It's on GitHub

Moving PHP open source forward - PhpStorm : The IDE that empowers PHP developers | The JetBrains Blog

Sponsorships 2025-2026

Opening Slack Jira Cloud links in the right browser - Rob Allen

The investigation

OpenIn's custom scripts

Helper functions

Do the work

That's it

Disabling the Zoom mini window on Linux - Blog entries :: mwop.net

Fixing PostgreSQL collation version mismatch - Rob Allen

Jumping to the end of bash's history - Rob Allen

Understanding All Relations Between Classes, Interfaces, Traits, and Enums in PHP - Exakat

Understanding Relationships Between Classes, Interfaces, Traits, and Enums in PHP

Key Takeaways

Converting JWKS JSON to PEM using Python - Rob Allen

Example

The script

Connect MCP Servers to Junie in PhpStorm - PhpStorm : The IDE that empowers PHP developers | The JetBrains Blog

About MCP PHP SDK

Junie + MCP

.gitattributes support