I think Joao missed the nuances of working inside a (locked) shared hosting environment.
However, if you need to make the correct rsync, have you thought about doing rsync pull from a shared host?
- I suppose to have some of the DSL routers and may resolve its external IP address.
- So that you can configure port forwarding from the rsync direct socket to your development area.
- So you can write a simple PHP (or any other) script that can wrap the rsync request in
proc_open()
. (I have a standard command for this on my shared service)
Well, the vulnerability here is that the rsync port will be publicly open to the Internet, and the direct socket method does not encrypt the payload, but you do not need to use the default value, and the service should only be running during rsync itself.
I just use the (delta) tarball of any updates and explodes locally as part of the release process to my hosting account, but rsync is there. In any case, it's worth a try.
$ remote rsync --version rsync version 3.0.6 protocol version 30 Copyright (C) 1996-2009 by Andrew Tridgell, Wayne Davison, and others. Web site: http://rsync.samba.org/ Capabilities: 64-bit files, 64-bit inums, 32-bit timestamps, 64-bit long ints, socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace, append, ACLs, xattrs, iconv, no symtimes rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the GNU General Public Licence for details.
TerryE
source share