Last modified: 2014-11-17 21:36:23 UTC
There is no way to debug CLI scripts with XDebug without documentation digging, as far as I can see. I usually add shell functions called xdebug_on and xdebug_off which export/unset XDEBUG_CONFIG='remote_host=10.11.12.1' (which then tells XDEBUG to use the standard vagrant host IP). What do you think of adding that to the vagrant user's bashrc?
Sure. just add env::var { 'XDEBUG_CONFIG': value => 'remote_host=10.11.12.1' } to the XDebug role. Submit a patch & I'll review.
Apparently there is no XDebug role anymore. I don't want to enable the debugger all the time (probably even enabling the debugger all the time the remote_debug role is enabled would be a bad idea). How about adding a scripts.d or profile.d directory to the vagrant user, which works like settings.d etc (anything in there is automatically executed when the user logs in, and puppet can drop its own scripts there, and not worry about overwriting a custom profile/bashrc file)? I could think of a few features besides this one where that would be useful.
(In reply to Tisza Gergő from comment #2) > How about adding a scripts.d or profile.d directory to the vagrant user, > which works like settings.d etc (anything in there is automatically executed > when the user logs in, and puppet can drop its own scripts there, and not > worry about overwriting a custom profile/bashrc file)? I could think of a > few features besides this one where that would be useful. The env:var and env::profile_script resources do just this. They add scripts in /etc/profile.d to be read during login shell initialization.
Bulk unassigning bugs from Ori.
