Skip to content

v5.2
Compare
Choose a tag to compare
@nicoverbruggen nicoverbruggen released this 29 Mar 15:43
· 882 commits to main since this release
v5.2
3227853

Upgrading

The recommended way of upgrading is running brew upgrade phpmon after you've installed PHP Monitor using Homebrew. This always gets you the latest and greatest stable version of PHP Monitor. If you did not use Homebrew to install the app, you can download a zip below (by expanding Assets and choosing phpmon.zip).

Important

If you do upgrade to Valet 3, you will lose support for PHP 5.6, but the site isolation feature will be enabled in PHP Monitor. For more information, I recommend reading my blog post on this release.

What's New

  • Updated site list window. The window has been updated to reflect the accurate PHP status (what version is being served). You will also see a pin icon for isolated sites (Valet 3 only).
  • Sort sites in site list. See also #148. In addition to the redesign, you can now sort your site list based on the various columns that have been added to the site list. You can reorder those columns the way you like, and the sorting you last applied will be remembered.
  • Default site support. See also #125. If you have specified a default site in config.json, it will now be displayed in the site list. Should you reload the site list, the config.json file is now also reloaded, which means that PHP Monitor will pick up any new default site, directories and TLD.
  • Easy CLI access to various PHP versions. PHP Monitor will detect what versions of PHP are installed and create helper files. You can then use them like this: pm80 will activate PHP 8.0, and pm74 will activate PHP 7.4. (PHP Monitor only enables which versions of PHP you have installed locally.)
  • Support for site isolation. See also #148. If you are running Valet 3.0 or newer, you can now choose a fixed version of PHP to use for each site. You can isolate a site by right-clicking on the site in question and selecting which version you'd like to isolate.

Resolved Issues

  • If your config.json file (containing your Laravel Valet config) is invalid, you will be prompted when PHP Monitor launches.
  • Added support for detecting Typo3 CMS projects using composer or the specific folder. (#153)
  • In certain situations, after installing or reinstalling PHP versions the www.conf pool configuration file would not be renamed, which is the default behaviour of Laravel Valet. PHP Monitor now disables those files whenever the version switch happens, because they could lead to failing services commands (#152). This brings the behaviour of PHP Monitor in line with Valet's own switcher.
Assets 3
Loading