SSH browser with rsync transfer engine

Re:SSH browser with rsync transfer engine by feelix on Sunday July 30, 2017 @02:02AM (#14884615)

> The remote machine must have a running SSH service and carry its own copy of rsync

Really the machine should just have to be running SSH. The UI could then take care of spooling up an instance of rsync on the target machine under the hood as soon as it connects.

[ Parent | on HN ]

Re:SSH browser with rsync transfer engine by scintill76 on Sunday July 30, 2017 @02:26AM (#14884668)

I think it means rsync must be installed. It probably starts rsync as you say.

[ Parent | on HN ]

Re:SSH browser with rsync transfer engine by rzzzt on Sunday July 30, 2017 @04:59AM (#14885082)

feelix is probably thinking of transferring an rsync binary first, when it is not available on the remote end.

[ Parent | on HN ]

Re:SSH browser with rsync transfer engine by tiernano on Sunday July 30, 2017 @07:12AM (#14885460)

How would you easily figure out which version to install? Having a requirement of rsync already installed on the box sounds reasonable, compared to having x86, x64, arm32, arm64, and the rest binaries in the client download...

[ Parent | on HN ]

Re:SSH browser with rsync transfer engine by scintill76 on Sunday July 30, 2017 @07:25PM (#14888436)

And that's not counting different OS's, different dependencies such as libc. In my opinion those things would be far out of scope for this project.

[ Parent | on HN ]

Re:SSH browser with rsync transfer engine by therein on Tuesday August 01, 2017 @11:48PM (#14907762)

I agree that it is beyond the scope of this project but a statically linked (with musl libc) rsync would be possible.

Like these guys: http://sta.li/

[ Parent | on HN ]

Re:SSH browser with rsync transfer engine by bonhardcomp on Wednesday August 02, 2017 @11:28AM (#14911300)

Nice. Am gonna be doing this.

[ Parent | on HN ]