@ricardomat, awesome. You're welcome.

@barry-hamilton, @Ricale-Kincheski, @k8nr, @marcelo-muller, @Moacir-Vilela-Sêga, thank you for reporting the problem. I do see I had a problem in the logs. I'm looking into it now.

@mark-hollis, thanks. I thought I had it fixed this morning and found out just recently it went down again. Working on it again now.

@riccardo-cereser, please try adding this to your script:

SCRIPTDIR=$(dirname "$0") cd $SCRIPTDIR

That way you can specify the full path to your script in the commands.json file, and when your script runs, it will cd to the directory where your script is.

@russ goodness! I rest easy knowing that there is no need to log in or issue any commands.
Thank you!!!

@renan-hugo, please try this:

Run which gulp to get the path to the gulp command. Like this:

russ@russmac % which gulp /Users/russ/.nvm/versions/node/v8.17.0/bin/gulp

Then make your shell script something like this:

#!/usr/bin/env bash cd /Applications/XAMPP/xamppfiles/htdocs/cative/wp-content/themes/cative/gulp/ /Users/russ/.nvm/versions/node/v8.17.0/bin/gulp assistir > /tmp/output.txt 2>&1

For some reason you need to specify the full path to the executables you install via npm i -g. That's been my experience on Mac anyways.

If that doesn't work, please try running the gulp script like this:

node /Users/russ/.nvm/versions/node/v8.17.0/bin/gulp

Or even like this:

/Users/russ/.nvm/versions/node/v8.17.0/bin/node /Users/russ/.nvm/versions/node/v8.17.0/bin/gulp

To do that last one, you'll need the full path to your node executable which you can find with this command:

which node