-
Notifications
You must be signed in to change notification settings - Fork 690
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 isolate proxy CLI commands do not respect custom site names #1272
Labels
Comments
Thanks, can you send in a PR? |
Hey @driesvints I can see a couple ways you could solve this - happy to try at a PR but just trying to work out what the best semantics would be, would using ie: |
Yes I think so 👍 |
aj-adl
added a commit
to framecreative/valet
that referenced
this issue
Aug 2, 2022
… commands Fixes laravel#1272 Adds support for passing in a custom sitename via the flag `--site=sitename` - Could be more flexible, at this point the '=' is mandatory - Code is repeated in two place, I thought it more likely that potential flags / checks diverge over time and didn't want to prematurely abstract Potential issues - someone calling a php command that requires a "--site" flag is not going to be able to pass it in. Other considerations - It would be better if the isolate function wasnt so tied to dir names - keeping a config file of isolated sites vs just parsing nginx configs seems better to me in the long run but is a larger and more serious refactor of valet. - We're a shop that uses valet for a lot of non-laravel stuff, and many legacy projects, so repo/folder names different to the domain is pretty common for us, less so for people on the golden path
aj-adl
added a commit
to aj-adl/valet
that referenced
this issue
Aug 2, 2022
Fixes laravel#1272 Adds support for passing in a custom sitename via the flag `--site=sitename` - Could be more flexible, at this point the '=' is mandatory - Command help updated, arguments added etc - Code is repeated in two place, I thought it more likely that potential flags / checks diverge over time and didn't want to prematurely abstract Potential issues - someone calling a php command that requires a "--site" flag is not going to be able to pass it in. Other considerations - It would be better if the isolate function wasn't so tied to dir names - keeping a config file of isolated sites vs just parsing nginx configs seems better to me in the long run but is a larger and more serious refactor of valet.
Going to close this as a PR was sent in. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description:
Firstly, I want to reiterate that the new features introduced in #1106 and #1216 are absolutely awesome, and have in general been a huge help.
This is really following on from #1206 - the PR there has fixed this issue for sites when running via FPM, but this fix doesn't carry over to the
valet php
andvalet composer
commands.It's pretty easy to see how this has happened - if you look at
valet/valet
Line 92 in bc56e30
valet/valet
Line 85 in bc56e30
which-php
without any additional arguments, butwhich-php
required the sitename to be passed in as an argument in order to work with domains that do not match the folder name.Steps To Reproduce:
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
~/.composer/vendor/laravel/valet/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
/usr/local/opt/php/sbin/php-fpm -v
sudo /usr/local/opt/php/sbin/php-fpm -y /usr/local/etc/php/8.1/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/usr/local/etc/nginx/valet/valet.conf\n---\n"; cat /usr/local/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'
sh -c 'for file in ~/.config/valet/nginx/*; do echo "------\n~/.config/valet/nginx/$(basename $file)\n---\n"; cat $file | grep -n "# valet loopback"; echo "\n------\n"; done'
The text was updated successfully, but these errors were encountered: