@dkocher commented

Either the current working directory must be the same as the script resides in (when executing ./cleanup.sh). If not cd to there first. Otherewise the path must be in your PATH environment variable to be excecuted globally.

As an enhancement the Send Command... invocation could change the working directory to the one opened in the browser itself.

macmedix commented

interesting! As a followup, I used Cyberduck to "send command..." and entered "pwd" to learn that the path is not as expected!
I'm using DreamHost.com, a major hosting company.
When I login (ssh or FTP) I connect as my username, then cd into the correct dir for that webs erver. What I see as the root (/) is not what pwd sees as the root.

Where I think I am:

/domainname.com/



Where FTP connections say I am:

/domainname.com/



where Cyberduck says I am:

pwd

/home/.margara/macmedix



Where SSH says I am:

[refresco]$ pwd

/home/macmedix/domainname.com

Interesting that the same question has 3 different answers. To try & run the script from Cyberduck, I used the "Send Command..." to say:

pwd

/home/.margara/macmedix

cd domainname.com

pwd

/home/.margara/macmedix

cd ..

pwd

/home/.margara/macmedix



So it appears that Cyberduck is not able to cd .. nor cd into a directory from the "Send Command..." Perhaps this is a result of how this webhost does things, but I can easily use Terminal or iTerm and SSH into the same host to move around and run scripts. I also tried the same test on my own OSX server, and it seems to me that CyberDuck was not able to "Send Command..." to cd up or into any folder. I connected using CyberDuck via SSH as root and was stuck in the root's home folder.

If it helps, I'm happy to give you a shell account on the web host so you can see it yourself.

Thanks very much for your time and consideration! I really appreciate it! :-)

Dave

@dkocher commented

Replying to [comment:2 macmedix]:
The issue is that the Command window in Cyberduck does not open a proper shell; e.g. bash. Therefore you can not rely on built-in features of a shell environment such as cd.

@dkocher commented

See also #3110.

albertoz commented

Hi, & thanks for CyberDuck. How difficult will be to open proper shell window (with correct path, & login) instead of CyberDuck's Command Window?

@dkocher commented

Replying to [comment:5 albertoz]:

Hi, & thanks for CyberDuck. How difficult will be to open proper shell window (with correct path, & login) instead of CyberDuck's Command Window?

This is already implemented. See Open in Terminal.