laravel-debugbar-companion
laravel-debugbar-companion copied to clipboard
Not working
companion keeps showing There are no current request yet. and i have configured the config file and restarted server
Same here.
Yep, same issue. I'm wondering if, in my case, this is a docker issue? Does this work with containers?
@jbxonline In a container, you would need to change the host IP-address. Is it possible to change your config in the config/debugbar.php
like this and fill in the host ip address:
'storage' => [
'enabled' => true,
'driver' => 'socket', // redis, file, pdo, custom
'path' => storage_path('debugbar'),
'connection' => null,
'hostname' => 'YOUR HOST IP ADDRESS HERE',
'port' => 2304
],
Hello, same issue here. Changed driver in config/debugbar.php to 'socket' (instead of 'app' proposed in client), and after debugging it creates and send data to socket, but the client (windows) is not processing the payload.
After enabling developers toolbar in windows client, it shows this:
seems like this is the problem:
@lubop This is fixed by commit 1f5fa4b34b1f2f9c21668cc0e6afcab7e897854e, but @mpociot didn't create a release yet. If you want, you can use the current master-branch.
@DavyDeCoster thanks, that was the problem. Managed to build release from current master branch and now it works...
@DavyDeCoster how do i then compile the code to an electron app executable by windows
@spartyboy install all dependencies using Yarn and then run yarn run build:win
should build a executable. If not, try yarn run publish:win
yea, indeed we need to wait for a new release, master branch it works fine.
Same here, waiting for a new release
@spartyboy install all dependencies using Yarn and then run
yarn run build:win
should build a executable. If not, tryyarn run publish:win
Thanks @DavyDeCoster, i was able to build the app from the master branch, it's working now
@spartyboy install all dependencies using Yarn and then run
yarn run build:win
should build a executable. If not, tryyarn run publish:win
$ yarn electron:build -- --win --x64 --ia32 -p always warning From Yarn 1.0 onwards, scripts don't require "--" for options to be forwarded. In a future version, any explicit "--" will be forwarded as-is to the scripts. $ vue-cli-service electron:build --win --x64 --ia32 -p always 'vue-cli-service' is not recognized as an internal or external command, operable program or batch file. error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. here is the error i get on trying to build it
@spartyboy i can send you the .exe installer, just let me know
@spartyboy i can send you the .exe installer, just let me know
pls do
For all those who need it, in the following link you can download the installer for Windows:
https://www.4shared.com/s/fW17WRXY1iq
This build was made by myself, no virus, no scam, no BS....just the debugbar companion ... !
@mpociot Any chance of getting a fixed release for Mac?
for anyone who - like me - googled this issue when looking how to set up debugbar companion to work with docker:
in docker-compose.yml
(add to container with laravel):
extra_hosts:
- 'host.docker.internal:host-gateway'
in config/debugbar.php
set
'storage' => [
'hostname' => 'host.docker.internal'
(...)
]
@mpociot could you please make a release for mac? Still doesn't work unfortunately. This issue resides here