-
Notifications
You must be signed in to change notification settings - Fork 698
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Valet link with --isolate doesn't pass custom name #1386
Comments
I found the The --isolate switch does read the .valetrc file, but use it only for the isolation of the folders name, not the custom link "foobar" provided |
I think we have two separate issues. @naabster would you mind spinning up a separate issue for that? |
I made a tiny bit of progress but then had to leave earlier than expected. Here's what I did: cd /tmp
mkdir linking-as-not-foobar
cd linking-as-not-foobar
echo "php=php@8.0" > .valetrc
valet link foobar --isolate and here's my error: So as we can see, we get this error when trying to isolate the directory: at /Users/mattstauffer/.composer/vendor/laravel/valet/cli/Valet/Site.php:182
Valet\Site->getSiteUrl() at /Users/mattstauffer/.composer/vendor/laravel/valet/cli/Valet/PhpFpm.php:171
Valet\PhpFpm->isolateDirectory() at /Users/mattstauffer/.composer/vendor/laravel/valet/cli/includes/facades.php:22 It's passing in the directory instead of the isolated short name. Hopefully that's an easy fix when I have a bit more time! |
I'm new to Valet and I stumbled upon this exact issue. I organize my projects something like this:
This incidentally results in the same issue:
It took me a while to figure it out—given the many different ways Valet resolves sites—but the issue stems from the A simple solution to this: provide the if (Site::phpRcVersion($name)) {
- $this->runCommand('isolate');
+ $this->runCommand('isolate --site="'.$name.'"');
} else { Unfortunately, this does not work since mnapoli/silly v1.8.1 which introduced an untested change to how sub-commands are handled as a consequence of a easily confusing error message from symfony/console. See mnapoli/silly#69 for further details, mnapoli/silly#70 for the fix of the dependency, and laravel/valet#1428 for the fix of this issue. |
Will be in today's release. Thanks all |
Description:
When running
valet link --isolate
with a custom name that doesn't match the directory name, such asvalet link foobar --isolate
, where the directory the site is in may be foobar.com, the isolate command doesn't seem to receive the custom name and ends up failing with the following validation error.Steps To Reproduce:
valet link --isolate foobar
Diagnosis
sw_vers
valet --version
cat ~/.config/valet/config.json
cat ~/.composer/composer.json
composer global diagnose
composer global outdated
ls -al /etc/sudoers.d/
brew config
brew services list
brew list --formula --versions | grep -E "(php|nginx|dnsmasq|mariadb|mysql|mailhog|openssl)(@\d\..*)?\s"
brew outdated
brew tap
php -v
which -a php
php --ini
nginx -v
curl --version
php --ri curl
/opt/homebrew/bin/ngrok version
ls -al ~/.ngrok2
brew info nginx
brew info php
brew info openssl
openssl version -a
openssl ciphers
sudo nginx -t
which -a php-fpm
/opt/homebrew/opt/php/sbin/php-fpm -v
sudo /opt/homebrew/opt/php/sbin/php-fpm -y /opt/homebrew/etc/php/8.2/php-fpm.conf --test
ls -al ~/Library/LaunchAgents | grep homebrew
ls -al /Library/LaunchAgents | grep homebrew
ls -al /Library/LaunchDaemons | grep homebrew
ls -al /Library/LaunchDaemons | grep "com.laravel.valet."
ls -aln /etc/resolv.conf
cat /etc/resolv.conf
ifconfig lo0
sh -c 'echo "------\n/opt/homebrew/etc/nginx/valet/valet.conf\n---\n"; cat /opt/homebrew/etc/nginx/valet/valet.conf | grep -n "# valet loopback"; echo "\n------\n"'
sh -c 'for file in ~/.config/valet/dnsmasq.d/*; do echo "------\n~/.config/valet/dnsmasq.d/$(basename $file)\n---\n"; cat $file; echo "\n------\n"; done'
The text was updated successfully, but these errors were encountered: