Repo backups saved me in this scenario. A developer did a fossil add *.* by mistake and committed. Well, that bloated our repo size tenfold. We knew quickly because push/pulls were taking too long. A query to this mailing list mentioned shun's and rebuilds, but I had already made some poor hacks to remove the offending files. I was trying to eliminate ~300 so manual shunning was out of the question. Fastforward - I went to a backup repo immediately prior to the offensive commit and started over. We regained our repo size and learned our lesson. In fact, it begs the question; Can I block any command that includes *.*? I asked about an automated shun, but shun is not available except through ui. :(
On Fri, Sep 5, 2014 at 3:52 PM, Warren Young <war...@etr-usa.com> wrote: > On 9/5/2014 13:36, Matt Welland wrote: > >> On Fri, Sep 5, 2014 at 12:10 PM, Ron W <ronw.m...@gmail.com >> <mailto:ronw.m...@gmail.com>> wrote: >> >> Still need to keep the Fossil repo backed up. >> >> Is there really a need for a backup if you have offsite fossils to which >> you regularly sync? >> > > Probably not. > > I do it anyway because I'm pretty irregular in how often I sync each > offsite clone to the master. It makes me feel better to have a cron job to > backstop me. > > This also allows me to do a few things differently than a simple fossil > clone sync: > > 1. "sqlite3 $repo .dump | xz > $repo.sql.xz" gives a somewhat smaller file > than the binary repo, and it is theoretically readable if you have to do > some deep disaster recovery. > > 2. You can follow that with a GPG pass to encrypt it for semi-secure > offsite storage, such as Dropbox or Google Drive. Running whole-archive > XZ-compressed data through GPG gives an attacker less of a foothold than > the individually-compressed blobs in the binary Fossil repo. > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
