I’m pleased to announce the immediate availability of PHP Monitor 5.6. This penultimate release of version PHP Monitor 5 brings a few new quality of life features to the app.
PHP Monitor 5.5 was released a while ago with new features like PHP Doctor (used to help you debug configuration issues) and a better onboarding experience (for those of you new to the app). Also added in version 5.5 was the ability to use custom environment variables.
Read blog postI am like most developers: the majority of the time, I cannot know (only anticipate) the future, so I write my code as succinctly as possible with reasonable room for flexibility. Life is good. But then reality comes knocking.
Requirements change. Features need to be added. Now your existing code needs to be modified in order for it to support these new constraints.
You think about a quick fix for a moment, but then you remember this:
“There is nothing more permanent than a temporary solution.”
You know what needs to be done. The dreaded refactor. Some of these refactors are absolutely not optional. They affect the foundation of your code. And if you don’t fix foundational issues soon enough, problems will soon become seemingly unfixable. The attempt to fix them will seem Herculean.
I’ve seen this happen plenty of times: when refactors are postponed, they are eventually forgotten or given up on. In practice this neglect caused issues for most projects: if not immediately, surely down the line.
Read blog postI’m pleased to announce the availability of PHP Monitor 5.4. This new release brings a bunch of new features to the app: both changes under the hood and powerful additions such as presets, or support for custom services.
This release took a bit longer to make and includes a set of rewrites under the hood: various views in the app are now being rendered with SwiftUI and should be more responsive.
The way services work have also changed: not only is it easier than ever to start or stop them from the menu, but it is also possible to bring your own Homebrew services to PHP Monitor and manage them from here.
Read blog postYou may know that as part of my principles behind PHP Monitor, I do not collect personal information. This means that I do not have access to automated crash log uploads. Instead, most of the time it is folks who see the app crash who end up reporting the crash.
Sometimes, it’s just faulty behaviour that pops up, but every now and then I get a hard crash report. Unfortunately, a crash report sent to me as a text file (.ips) means that I need to figure out what went wrong.
Read blog post