91–100 of 117 posts
I like it! But for me ssh already provides a simple and secure way to move files from one place or another.. tar -cf - ./files.txt ./orDir/ | ssh host "(cd /dest/dir; tar -xf -)" Given that ssh it so ubiquitous I think this will always be my go to.
What about good old scp? scp file.txt user@host:/dest/dir/
Earlier quoted context omitted.
> tar -cf - ./files.txt ./orDir/ | ssh host "(cd /dest/dir; tar -xf -)" You should use '&&' instead of ';' on the host side. That way you don't accidentally dump your transfer contents into a wrong directory if the existing host dir doesn't exist. e.g.: tar cf - stuff | ssh host "(cd /dest/dir && tar xf -)"
Or just skip the shell entirely: tar -C /dest/dir -xf -
There used to be a service called chunk.io that did this. Then, presumably by some combination of becoming popular causing them bandwidth/storage issues or their service being abused, they had to make it invitation-only. (The site still exists, but they never replied to my e-mail to their signup address, so I can't say for sure if they're still live or not.) I wish transfer.sh good luck, and will bookmark them for no…
Earlier quoted context omitted.
> tar -cf - ./files.txt ./orDir/ | ssh host "(cd /dest/dir; tar -xf -)" You should use '&&' instead of ';' on the host side. That way you don't accidentally dump your transfer contents into a wrong directory if the existing host dir doesn't exist. e.g.: tar cf - stuff | ssh host "(cd /dest/dir && tar xf -)"
Or just skip the shell entirely: tar -C /dest/dir -xf -
Earlier quoted context omitted.
If you can trust to have gnu tar on both side, you can reduce typing. I usually do: tar c files.txt orDir | ssh -C host tar x -C /dest/dir
What about just typing rsync -havz --progress source destination? -h for human-readable numbers -a for archive mode -v and --progress for verbose info -z for compression during transfer Add a -n for a dry run if required. https://linux.die.net/man/1/rsync One of the people who came up with it - Andrew Tridgell - was more or less "responsible" for Linux and BitKeeper parting ways, which in turn ultimately lead to the…
--info=progress2
You can use it since rsync version 3.1.0.
woof -i -p woof: http://www.home.unix-ag.org/simon/woof.html 1. Allows directory upload/download (tar/gzip/bzip2 compressed) 2. Local file server (doesn't go over the internet) 3. Allows upload form (-U option) 4. Allows file to be served number of times (-c option)
Earlier quoted context omitted.
I usually go straight to tar & ssh over scp since you can do directories where you can't with scp. But yeah, if you just have some files scp works.
You can obviously send directories with scp, just use -r. Or am I missing something?
There are so many tools that can transfer files between two computers. I really like ones like this because you don't have to have SSH access or forward any ports to send a file from A to B. Its similar vein to other peer-to-peer utilities like zget [1], sharedrop [2], instant.io (webtorrent) [3], filepizza (webtorrent) [4], magic-wormhole [5], toss [6], dat [7], and many many others. During Hacktoberfest I also star…
Earlier quoted context omitted.
I usually go straight to tar & ssh over scp since you can do directories where you can't with scp. But yeah, if you just have some files scp works.
You can obviously send directories with scp, just use -r. Or am I missing something?