Skip to content
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

Can't use absolute path in transfer #97

Open
mik01aj opened this issue Jul 22, 2015 · 3 comments
Open

Can't use absolute path in transfer #97

mik01aj opened this issue Jul 22, 2015 · 3 comments

Comments

@mik01aj
Copy link

mik01aj commented Jul 22, 2015

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.

@pstadler pstadler added the bug label Jul 23, 2015
@pstadler
Copy link
Owner

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.

@mik01aj
Copy link
Author

mik01aj commented Jul 23, 2015

Thanks for the reply.

I did it just like this, and it works.

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.

@StyleT
Copy link

StyleT commented Jan 22, 2016

Have same issue, I think that I should be able to use any path I want.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants