willvincent

@vladimir Right, valet is only designed to handle a single tld, because in 99% of cases that's all anyone should need.

However, just because it's limited that way does not mean you cannot leverage the same infrastructure, nginx, php, and mysql that valet uses. The nginx config loads virtualhost config from ~/.valet/Nginx so all you'd need to do is add config file(s) there, and then define your host names in the hosts file.. as you'd do with a normal MAMP setup... as I said. ;)

Your only other option, with valet, would be that you might be able to force it to work with custom valet drivers, the api allows for mutating the uri, which you might be able to leverage to alter the domain...

Honestly though, if you're working with a team that large you should be using vagrant, or docker or something otherwise the chances of running into "it works on my machine" issues is extremely likely. With a team that size you definitely want to ensure everyone has as close to identical environments as possible. In a perfect world your dev environment should always match that of the production environment -- in terms of specific versions of each piece of the stack, plugins enabled, memory allotted, etc. Tools like vagrant and docker make such things pretty painless across large teams. Avoid/ignore them at your own peril I guess. :)

Return to Thread...