Thus said [email protected] on Sat, 09 Aug 2014 09:46:37 -0000:
> I'm using what I believe is probably a common setup: I have a server > on my private network here containing the "canonical" repositories for > all my projects. I have clones of these repositories on all machines > here, and the repositories on the server are backed up nightly. I then > have public-facing repositories on io7m.com which are basically > read-only public mirrors of my own private repositores (I have no > contributors): If none of your public-facing repositories accept commits, wiki edits, or tickets, or in otherwords are completely read-only, you could stage the public-facing repositories on your local system and then use rsync to copy them to your io7m.com host. This should be fairly efficient. It would use a single SSH connection to the server and should be short lived given that rsync will only transfer blocks of data that have changed. 1) clone all your canonical repositories to a local directory without a Fossil user (nobody/anonymous clone in other words). 2) rsync -avz -e ssh local/ [email protected]:path/to/repos/ Then when you need to update the remote: 1) fossil pull all staged local repositories from canonical source 2) rsync -avz -e ssh local/ [email protected]:path/to/repos/ If you want to see how efficient rsync is, you can add the --stats during the updates to remote. How would this work out for you? Andy -- TAI64 timestamp: 4000000053e64b2a _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
