laravel-valet

Laravel valet won't install

由 我的未来我决定 提交于 2019-12-13 02:55:40
问题 I had some problems with valet. I have used it for a while no. No i like to reinstall valet. But i don't get it installed. This is what i did before (whit help) Error installing php 71 with homebrew on my mac After this i got my homebrew running: brew list: brew list apr c-ares glib libev libpq mysql python webp apr-util curl-openssl gmp libevent libsodium nghttp2 readline xz argon2 freetds icu4c libffi libssh2 openldap rtmpdump aspell freetype jansson libidn libtiff openssl sqlite autoconf

Permission based issue with Valet (so it seems)

由 三世轮回 提交于 2019-12-11 18:01:09
问题 I got Valet to work and .test domains can be pinged etc. However, when I create a laravel new test-site I get a bunch of permission-based errors. I 'sudo'd' the laravel build but I was repeatedly warned not to do this. If I then view the site on the browser this is the error I get: and this: So - is the problem that I placed my "sites" folder (which I can "builds") in an inappropriate section of my machine? 回答1: You need to give permission to your storage directory. In my local mac I

Laravel passport trying to get oauth/token. Guzzle keeps hanging, also on other Guzzle calls

由 坚强是说给别人听的谎言 提交于 2019-12-11 14:32:40
问题 Set up a new project with Laravel 5.8 and I also installed Laravel Passport & Guzzle. Created a local server with php artisan serve on port 8000. Postman is able to get a response at /oauth/token (but only when the body is in JSON). When I try to access the API through a controller method my browser returns a 500 error and no errors are showing up in the logs. When I try to point guzzle to the same controller method through a route postman keeps loading and it's even needed to force close my

Laravel Valet sites connection refused on port 80

由 ε祈祈猫儿з 提交于 2019-12-11 06:58:40
问题 Ever since Chrome and Safari started forcing HTTPS redirection on the .dev TLD I've been getting issues connecting to my Laravel Valet sites. Without knowing that Chrome and Safari had done this, I updated Valet to from 1.2 and not thinking to check in Firefox first (doh! 😖). I've installed the latest stable release of Laravel Valet (2.0.6) on High Sierra (10.13.2), completely removed the running version of homebrew/php/php70 and reinstalled to be sure and have now changed the TLD to .test. I

Laravel valet It works

由 一个人想着一个人 提交于 2019-12-09 09:53:56
问题 I'm trying to install Laravel valet but I keep getting (when I visit domain.dev): It works! I already tried a lot. For example: remove valet stop apache (apachectl stop) composer global require laravel/valet valet install valet restart But that does not work for me. I've also installed Laravel Homestead in a vagrant box. Perhaps that has something to do with it? I can visit my Homestead sites. How can I fix this problem? 回答1: "It works!" will always be a message from Apache. Apache has to be

Laravel Valet not working. 127.0.0.1 Connection Refused

由 我的未来我决定 提交于 2019-12-08 02:52:08
问题 Trying to get the valet setup working. It appears when accessing 127.0.0.1 the connection is refused which is the message I get when I go to one of the *.dev sites setup. I've made sure apache is stopped and have been Googling all over the place and unable to find a solution. Has anyone come across this or have any ideas on what to try next? I previously had httpd22 installed but I've now uninstalled this with brew which changed the 127.0.0.1 from responding with a list directory of /Users

Laravel Valet not working. 127.0.0.1 Connection Refused

由 风格不统一 提交于 2019-12-06 13:27:02
Trying to get the valet setup working. It appears when accessing 127.0.0.1 the connection is refused which is the message I get when I go to one of the *.dev sites setup. I've made sure apache is stopped and have been Googling all over the place and unable to find a solution. Has anyone come across this or have any ideas on what to try next? I previously had httpd22 installed but I've now uninstalled this with brew which changed the 127.0.0.1 from responding with a list directory of /Users/Rick/Sites to now connection refused. Fixed this. I followed a guide a while back to get a local dev

Laravel valet not working

由 青春壹個敷衍的年華 提交于 2019-12-04 20:51:39
问题 I use OSX El Capitan and PHP 7. I followed the installation guide so I install Laravel Valet version v1.1.3 successfully. I ping foo.dev or any.dev then the terminal prints "64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.116 ms" Everything is ok. My directory /User/mickey/Sites is added to Valet's paths. I created a Laravel 5.2 project named blog, then run the project with php artisan serve ok but when i accessed url blog.dev on the browser, the browser said This site can’t be reached,

Laravel Valet - This Site Can't Be Reached

由 假装没事ソ 提交于 2019-12-04 14:41:08
I have successfully followed the Setup a Mac Dev Machine until this tutorial: https://laracasts.com/series/setup-a-mac-dev-machine-from-scratch/episodes/10?autoplay=true The problem is that when I go to SITENAME.dev , nothing shows up. Instead, I get the following message: This site can’t be reached test2.dev refused to connect. Did you mean http://test2.de/ ? Search Google for test2 dev ERR_CONNECTION_REFUSED I've tried this both for a laravel install (using the laravel installer) and a wordpress install. Neither one works. Any idea why it is not working. I have followed the course step-by

Laravel valet not working

由 天大地大妈咪最大 提交于 2019-12-03 13:55:28
I use OSX El Capitan and PHP 7. I followed the installation guide so I install Laravel Valet version v1.1.3 successfully. I ping foo.dev or any.dev then the terminal prints "64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.116 ms" Everything is ok. My directory /User/mickey/Sites is added to Valet's paths. I created a Laravel 5.2 project named blog, then run the project with php artisan serve ok but when i accessed url blog.dev on the browser, the browser said This site can’t be reached, blog.dev refused to connect. ERR_CONNECTION_REFUSED. I don't know what is the problem with my installation
订阅 laravel-valet