You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I give an absolute path as the local path to local.transfer, it treats the path as if it was relative (so if I specify /tmp/package.tar.gz, it trats it as ./tmp/package.tar.gz.
The text was updated successfully, but these errors were encountered:
This is a limitation of how the transfer function utilizes rsync. The simplest solution I can think of would be to create or move package.tar.gz into the current project root and then call:
local.transfer('package.tar.gz','/tmp');
This also makes sure that you don't create unwanted sub-directories on the remote hosts.
I understand that implementing absolute paths might be hard, but even if you don't, the transfer function should recognize that it got an absolute path and fail with a message like "absolute paths are not supported, sorry". At least, that's what I'd expect.
When I give an absolute path as the local path to
local.transfer
, it treats the path as if it was relative (so if I specify/tmp/package.tar.gz
, it trats it as./tmp/package.tar.gz
.The text was updated successfully, but these errors were encountered: