Feature request: Optional use of Valet

[skylerkatz]

Hello!

I totally love the app, but I do not currently use valet. I installed it locally just to use the app. I was wondering if there was an easy way to make the valet portion of the app optional, so if you don't have valet installed, you can still access the PHP specific features/functionality?

I would be willing to attempt a PR, but could use some guidance about where to begin looking, as I have never worked on an xcode app before.

Thanks,
Skyler

[nicoverbruggen]

Here's my take: ditching Valet as a requirement makes a variety of things more difficult than they need to be. Users would have to do a lot of setup, kind of defeating the purpose of the app. I don't think that's something I'm looking for in the app right now.

If you want to, you can install Valet and not use it, and keep using PHP Monitor to switch between PHP versions, for example. (Valet doesn't use any additional resources in the background because it's just Homebrew services under the hood with some preset configuration. You are always in control of the Homebrew services too, so you can do whatever you like.)

Is there any reason you'd want to avoid using Valet? I think I understand why people ask this, but I'd love to hear your reason for asking for this change. I've converted this to a discussion thread should other people want to chime in.

[skylerkatz]

I totally understand, and will probably continue to leave valet installed, but unused.

At my current job, we have a couple of applications that run on rails using pow and it does not play nicely with valet. As a result, we run our php apps (some are laravel, others are vanilla php) using Vagrant and Docker.

Valet is great, but we have a number of different developers on the team, with different hardware, so in our case, vagrant/docker ended up being the easiest approach, granted both add some level of complexity.

[nicoverbruggen]

What's the conflict specifically? Is it the .test TLD? Because you can tweak that too (in .config/valet/config.json).

EDIT: The easiest way is to run: valet tld {newtld}

If there's anything I can do to make the "keep Valet installed with minimal conflicts" process easier that doesn't require the removal of Valet entirely, I don't mind making some changes / adding some stuff.

[skylerkatz]

Honestly, it was about two years ago the last time we tried to use everything together. I do know that the issue was not related to the TLD. It is possible it was related to ports, but that seems like it would have been a solvable issue.

Our apps also use different versions of PHP, Redis, MySQL, Postgres and Ruby, which Docker is able to solve for. The land of legacy is a bit of a minefield :)