-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
local.transfer filesToCopy path problem #151
local.transfer filesToCopy path problem #151
Comments
I also with the same problem. |
Hey there. Unfortunately this is limitation of rsync. You could try to work with absolute paths or create a tar file (probably in /tmp), transfer this to the remote servers, untar it and continue from there. This has several advantages over copying a bunch of small files. |
By the way, why use the tmp file instead of direct upload origin file? What are the benefits of doing so? |
This is the only way to ensure compatibility with various operating systems and rsync versions. See here |
Copy file instead of origin file to transfer is hack, but it's the only way to resolve it. |
I wanna rsync one file to server,
filesToCopy
is['../aaa.conf']
, whenlocal.transfer(filesToCopy, remoteDir)
,they will be errorfailed: No such file or directory
,because that rsync file path is current path connectfilesToCopy
,just like/code/project/test/../aaa.conf
not/code/project/aaa.conf
The text was updated successfully, but these errors were encountered: