On 2014-08-09T10:23:35 -0600 "Andy Bradford" <[email protected]> wrote: > > 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.
I have considered this before, and I already use rsync for nightly backups. However, I'm hesitant to use it for this because, even though the repositories on io7m.com are conceptually read-only, I do forsee people eventually filing tickets on them should I one day start actually promoting any of the software I write and gain users. Having heard everything suggested on here, I'm leaning towards storing the ID of the tips of each repository and syncing only when they change. I'll do an unconditional sync once a day in order to pull in anything that may have been unexpectedly added on the io7m.com side. I don't suppose there's any way to make fossil hit a given URI whenever the current repository receives artifacts? M _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
