Pre-release testing thread: v4.1

[nicoverbruggen]

I'm currently looking for people who would like to test run the next pre-release version of PHP Monitor.

If you are curious which changes have been made since v4.0, please use GitHub's comparison tool to compare main to develop.

Latest pre-release build

v4.1-rc4

Download link:
phpmon-4.1-rc4.zip

This release candidate includes support for detection of your linked and parked sites. The changes to the version switcher have been postponed to v5.0. (See #34 for more information.)

RC2 now includes a check that determines whether your version of Valet is equal to or newer than v2.16.2, which is the recommended minimum version. You'll see an alert if your version is too old and unsupported. Please upgrade if you see this alert!

You can access this functionality via PHP Monitor > View linked & parked domains... You can right-click after selecting a site to see common interactions (like open in your favorite editor, or open in your browser / Finder).

I'm looking for feedback mainly related to the version switcher and the domain list.

• Does the app crash at launch?
• Does the domain list detect all the domains correctly?
• Can you use the secure/unsecure domain feature correctly?
• Are you able to launch the various apps and open the correct folder using the right-click menu in the domains list?

Feedback would be appreciated. Please respond below in this particular thread.

[ashleyshenton]

For my use case I preferred the old switcher. This is because when switch down to PHP 7.1 I can't then switch back to a higher version as I have a composer global dependency that prevents it, even though this doesn't affect the development of the site while 7.1 is running. I know this because I had the same issue when using valet use myself. The error I get in the command line is

~ valet use [email protected]

Fatal error: Composer detected issues in your platform: Your Composer dependencies require a PHP version ">= 7.3.0". You are running 7.1.33. in /Users/***/.composer/vendor/composer/platform_check.php on line 24

I know I could alter my global dependencies and composer update but it's a bit more tedious.
Would it be possible to have an option to choose which switcher to use? I started using PHP Monitor as it helped me circumvent this issue.

• Does the app crash at launch?
  App opens with no issues.
• Does the version switcher work as expected? Is the correct version of PHP linked?
  Version switcher works great other than the issues above.
• Is the version switcher noticeably slower than before, or is the difference minimal?
  Switching seems quite a bit slower but not so much that it's a problem.
• Does the domain list detect all the domains correctly?
  Valet linked sites all show for me and display accurately.
• Can you use the secure/unsecure domain feature correctly?
  This feature works correctly for me.
• Is your installation of Visual Studio Code and/or PhpStorm being detected correctly?
  I don't get the option to open in PhpStorm despite having it installed. I have it installed through Jetbrains Toolbox if that makes any difference.

[ashleyshenton]

Hi @nicoverbruggen, thanks for the new build. I've just given it a try and the new switcher option in preferences is great.

Unfortunately, the 'Open with PhpStorm (via Toolbox)' option in the linked domains doesn't work. When I have a project already open, it just takes me to that window. When I full close PhpStorm and try again, it just opens up the 'Welcome to PhpStorm' window where the project browser is but goes no further than this.

[nicoverbruggen]

Hmm, okay, thanks for letting me know! I only did a quick test and saw that PhpStorm launched, so I didn't think anything of it. I probably had the project open from the last time I launched the app manually. I think I might just have to change my approach for this one.

In PhpStorm, you can go to Tools > Create command line launcher which generates a /usr/local/bin/pstorm binary. That's what I'll be using instead in the next build. This is the best way to open any file or directory, since it doesn't care where your PhpStorm installation is located.

I'm guessing the usual command that I used (invoking open -a /appname) doesn't work with the Toolbox version since that one is located in your ~/Applications/JetBrains Toolbox directory but linked to a different path. Strange.

I'll make the changes later this week to ensure the pstorm binary is used if detected. In order to make this easier to discover, I've filed issue #67.

[nicoverbruggen]

@Diagnost1X I've just uploaded beta 5 (see original post above). If you could let me know if opening a folder with PhpStorm works correctly now, that would be great!

(If you do not have pstorm linked in /usr/local/bin/pstorm, then PHP Monitor will provide you instructions. Otherwise, it should just work... fingers crossed.)

Thanks!

[ashleyshenton]

My phpstorm is linked at /usr/local/bin/phpstorm and you can't use the `Create command-line launcher' when you use Toolbox.

Article from image: https://blog.jetbrains.com/blog/2018/08/23/toolbox-app-1-11-whats-new/

I have my Toolbox set to look in /usr/local/bin which means I can use phpstorm in the terminal. I suppose I could symlink pstorm to get this working but not sure if you want to build it into the app.

[nicoverbruggen]

Oh, so the default for Toolbox is to generate phpstorm as the default name for the script located in /usr/local/bin?

It‘s unfortunate then that the Toolbox app suggests a different script from the standalone install. (pstorm vs phpstorm)

If you symlink /usr/local/bin/phpstorm to /usr/local/bin/pstorm, the app should work correctly... can you confirm this is the case? If so, I'll just detect either of those in the app. It’s an easy thing to change.

EDIT: I believe I have found a better way to handle this that doesn't require any of this. Hope to have it ready for beta 6. 😎