Skip to content

v6.2
Compare
Choose a tag to compare
@nicoverbruggen nicoverbruggen released this 29 Oct 10:30
· 114 commits to main since this release
v6.2
20d19f2

PHP Monitor 6.2 is a minor update that comes with a bunch of fixes and adds a configuration editor which currently lets you edit the following: memory_limit, post_max_size and upload_max_filesize via the GUI.

How to install or upgrade

⚠️ PHP Monitor 5.8 and newer require macOS Monterey 12.4 or newer! Learn more here.

If you have an existing PHP Monitor.app in your Applications folder you can use the built-in updater.

If you haven't installed PHP Monitor yet, you can click here to download the app. Place the app in your Applications folder and you may want to consult the README file for some more information.

What's New

🆕 A simple configuration editor has been added!

You can now edit the maximum memory limit, max POST size and the maximum upload size with PHP Monitor. If you are using Valet and the memory-limits.ini stub file is missing, PHP Monitor will attempt to restore it. As you adjust the values, PHP Monitor will try to dynamically apply the memory limits.

This is the first version of the configuration editor, and it will be expanded in the future. If you encounter any bugs while using this feature, please get in touch via an issue.

What's Fixed

  • PHP Monitor now generates scripts compatible with Fish in ~/.config/phpmon/bin if your default shell environment is Fish. For more details on how to use these, please see the write-up here. (#264)
  • Fixed an issue where the type of projects in the Domains window would not be detected correctly. (#263)
  • Fixed an issue with some windows not coming to the front after selecting a menu item if another application had the focus (on macOS Sonoma only). Windows are now brought to the front by using window?.orderFrontRegardless(), which should resolve this problem.
  • Added detection of Laravel Herd, which may conflict with a standalone Laravel Valet installation (installed with composer global install laravel/valet). During startup of PHP Monitor, the app will now require you to terminate Laravel Herd. You can start Laravel Herd afterwards, but this is currently not supported.

Note: Ensuring that PHP Monitor does not conflict with Laravel Herd is very much a temporary solution, as I will try to ensure that PHP Monitor and Herd can integrate better in the future.

Assets 4
Loading