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

Enabling xdebug by default via vvv-init.sh #332

Closed
sc0ttkclark opened this issue Apr 18, 2014 · 6 comments
Closed

Enabling xdebug by default via vvv-init.sh #332

sc0ttkclark opened this issue Apr 18, 2014 · 6 comments

Comments

@sc0ttkclark
Copy link
Contributor

I'd like to enable xdebug by default, but adding something like vagrant ssh -c xdebug_on won't work, is there a way that someone knows how to do that easily?

@westonruter
Copy link
Contributor

Doesn't work in what way? On my command line, I do:

$ vagrant ssh -c xdebug_on
 * Restarting PHP5 FastCGI Process Manager php5-fpm     [ OK ]
Connection to 127.0.0.1 closed.

So it works fine. Are you trying to invoke this inside of your vvv-init.sh script? This won't work as-is, because it runs inside of Vagrant and so you'd call xdebug_on directly. And you may need to use the full path: /home/vagrant/bin/xdebug_on

Alternatively, you could add this to a provision-post.sh file.

@sc0ttkclark
Copy link
Contributor Author

I tried xdebug_on too, but I'll try the full path next. Thanks!

@sc0ttkclark
Copy link
Contributor Author

Full path worked, adding this to my vvv-init.sh:

/home/vagrant/bin/xdebug_on

No VVV provisions to set it on by default, which is what me needs!

@andrezrv
Copy link
Contributor

Maybe not needed anymore, but you can also do it by adding this to your Customfile:

config.vm.provision "shell", inline: "xdebug_on", privileged: false

@Mte90
Copy link
Member

Mte90 commented Mar 17, 2015

for me this line in Customfile not work.
I use this command for launch vvv and xdebug:
vagrant up; vagrant ssh -c xdebug_on

@lock
Copy link

lock bot commented Feb 23, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Feb 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants