Skip to content
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

Laravel dump-server does not log anything on console #34

Open
cosecantt opened this issue Sep 29, 2018 · 10 comments
Open

Laravel dump-server does not log anything on console #34

cosecantt opened this issue Sep 29, 2018 · 10 comments

Comments

@cosecantt
Copy link

Laravel upgraded from 5.5->5.6 then 5.6-.5.7

I can run following command

php artisan dump-server

shows following:

 [OK] Server listening on tcp://127.0.0.1:9912
 // Quit the server with CONTROL-C.

But

dd($user)

does not log on the console. Instead it shows on the browser.

@JulianMar
Copy link
Contributor

you need to use the dump function not die and dump

@jagroop
Copy link

jagroop commented Oct 2, 2018

@cosecantt
Copy link
Author

you need to use the dump function not die and dump

I've tired both dump() and dd(). It does not work either.

@mpociot
Copy link
Member

mpociot commented Oct 4, 2018

@cosecantt what's your server setup? Are you using homestead/docker/valet?

@cosecantt
Copy link
Author

I am using following:

PHP 7.2.9
Homestead v7.17.00
Vagrant 2.1.4
Oracle VirtualBox Version 5.2.18 r124319 (Qt5.6.2)
Windows 10 64bit

Upgraded from Laravel 5.5 to 5.6 and 5.6 to 5.7 following the upgrade manual on documentation

@ctrlaltdylan
Copy link

Similar issue but with different setup. And I did use the dump() function as described in the docs:

PHP 7.1
Running locally with php artisan serve
php artisan dump-server also running a different pane

No output.

@aurawindsurfing
Copy link

aurawindsurfing commented Nov 26, 2018

Same issue using:

Laravel Valet 2.1.1
PHP 7.2.10

it works however in laravel telescope but not with each request.

@BobbyBorisov
Copy link

@mpociot i am using it with docker? should it work out-of-the-box with it or i need to configure something

@matijakovacevic
Copy link

i got this problem also...

the real problem was i installed laravel telescope, went to the url and afterwards started dump-server...
all my dumps() went to telescope...
after closing telescope and restarting dump-server, everything started showing correctly

@xtrasmal
Copy link

[STARLOG / entry / day 1028 - talking at the void]

I've been out here so long that I actually miss the browserwars that made me leave earth in the first place. Anyways.. while gooogling I found this page and suddenly it hit me... an old familiar memory. I realised I am running all stuff in a virtual machine. Well.. mind you.. it's not that I didn't know.. I boot the damn thing everyday. It's more that coffee in deep-space works differently. It floats and you need to take bites out of it, then do gyro exercises hoping the coffee reaches your stomach.

So since this ticket is still open and I type at least 35 WPM with a accuracy of at least 10%, I wanted to add this obvious fact:

Start php artisan dump from the within the machine. The real localhost(tcp://127.0.0.1:9912).

127001-wallpapers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants