2
submitted 10 months ago* (last edited 10 months ago) by theorangeninja@sopuli.xyz to c/selfhosted@lemmy.world

Hello selfhosted! Sometimes I have to transfer big files or a large amounts of small files in my homelab. I used rsync but specifying the IP address and the folders and everything is bit fiddly. I thought about writing a bash script but before I do that I wanted to ask you about your favourite way to achieve this. Maybe I am missing out on an awesome tool I wasn't even thinking about.

Edit: I settled for SFTP in my GUI filemanager for now. When I have some spare time I will try to look into the other options too. Thank you for the helpful information.

top 16 comments
sorted by: hot top controversial new old
[-] Turboblack@lemmy.world 1 points 10 months ago

you can use a regular ftp server with administrator and user rights, distribute rights to those who replenish, and those who just take - guests at home I transfer in this way from computer to computer without connecting them to a common network, what could be simpler? why invent some ways with keys or bash if there is a 40-year-old technology that just works great, and to open ftp it is enough to enter the IP address in the explorer

[-] possiblylinux127@lemmy.zip 1 points 10 months ago

What do you mean by specifying IP address?

[-] sugar_in_your_tea@sh.itjust.works 1 points 10 months ago

What's wrong with rsync? If you don't like IP addresses, use a domain name. If you use certificate authentication, you can tab complete the folders. It's a really nice UX IMO.

If you'll do this a lot, just mount the target directory with sshfs or NFS. Then use rsync or a GUI file manager.

[-] merthyr1831@lemmy.ml 1 points 10 months ago

rsync over an SMB share was pretty seamless.

[-] lemming741@lemmy.world 1 points 10 months ago

sftp

All my machines have my keys, nothing to set up, nothing to tear down.

[-] linuxguy@lemmy.gregw.us 0 points 10 months ago
[-] atzanteol@sh.itjust.works 0 points 10 months ago
[-] blackbrook@mander.xyz 0 points 10 months ago

SCP, the protocol, is deprecated. scp, the command, just uses the SFTP protocol these days. I find its syntax convenient.

[-] atzanteol@sh.itjust.works 0 points 10 months ago

Oh does it? I didn't realize that. I've just switched over to rsync completely.

[-] blackbrook@mander.xyz 1 points 10 months ago* (last edited 10 months ago)

Since OpenSSH version 9.0, so like mid '22. So as long as you're not running something more out of date than that.

[-] Kit@lemmy.blahaj.zone 0 points 10 months ago

Not gonna lie, I just map a network share and copy and paste through the gui.

[-] theorangeninja@sopuli.xyz 0 points 10 months ago

Sounds very straight forward. Do you have a samba docker container running on your server or how do you do that?

[-] drkt_@lemmy.dbzer0.com 2 points 10 months ago* (last edited 10 months ago)

I just type sftp://[ip, domain or SSH alias] into my file manager and browse it as a regular folder

[-] cass80@programming.dev 0 points 10 months ago

Snapdrop if they both have a gui/webbrowser. https://github.com/SnapDrop/snapdrop

Scp otherwise

[-] theorangeninja@sopuli.xyz 1 points 10 months ago

I used that before but usually I prefer the fork of snapdrop, pairdrop or localsend. Might want to try magic wormhole one day.

[-] westingham@sh.itjust.works 1 points 10 months ago

Or https://github.com/schlagmichdoch/PairDrop if you don't want to support a project bought out by LimeWire

this post was submitted on 18 Mar 2025
2 points (100.0% liked)

Selfhosted

54767 readers
68 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS