Warden command for xdebug from CLI

clixdebug.cmd

#!/usr/bin/env bash
[[ ! ${WARDEN_COMMAND} ]] && >&2 echo -e "\033[31mThis script is not intended to be run directly!" && exit 1

source "${WARDEN_DIR}/utils/env.sh"
WARDEN_ENV_PATH="$(locateEnvPath)" || exit $?
loadEnvConfig "${WARDEN_ENV_PATH}" || exit $?
pushd "${WARDEN_DIR}" >/dev/null

# docker exec -ti <CONTAINER_ID> php -d xdebug.remote_autostart=on -d xdebug.remote_host=host.docker.internal bin/magento
containerid=$(docker ps -qf "name=debug")
#echo $containerid;
if [[ $containerid != "" ]]; then
	echo "xDebug executing on container ... ${WARDEN_PARAMS[0]}";
	docker exec -ti $containerid php -d xdebug.remote_autostart=on -d xdebug.remote_host=host.docker.internal "${WARDEN_PARAMS[@]}" "$@"
else
	echo "A container image named 'debug' was not found.";
fi

gistfile1.txt

Save above file to /usr/local/Cellar/warden/[x.x.x]/commands/clixdebug.cmd (replacing [x.x.x] with version)

Usage:
`warden clixdebug <php-script-file>` 

NOTE: full path not needed.

Example how-to execute via warden:

`warden clixdebug bin/magento`

Just an update

Now, there's a command warden debug
when this is run the user is launched into a shell similarly to when warden shell is run, but in this case the shell is opened by default within the php-debug container.

more details: wardenenv/warden#33 (comment)

@chapagain Thanks for the update! Glad to hear it's included in warden out of box now. Cheers! 👍