Version 0.2.0 of bfsync

Release Notes: This release is an almost complete rewrite. It is no longer based on git, but uses an SQLite database to store the content. A FuSE filesystem is now used to view/edit the repository contents. The version history was improved, so it is possible to directly access old versions via the FuSE filesystem. This release also stores more metadata than the old one, so user and group, hardlinks, devices, and so on are supported. It provides code to interactively handle merge conflicts (for instance if the file X was independently modified in two checkouts).

Other releases

  •  18 Apr 2013 14:40

Release Notes: This release added a new "bfsync need-upgrade" command, which returns whether the bfsync repository needs to be upgraded to the current bfsync version. Some build problems related to Boost were fixed, as well as issues that caused building on Debian/squeeze to fail.

  •  19 Mar 2013 21:53

Release Notes: This release adds a bfsync diff command which compares the last and current version of a file stored in a bfsync repository using diff. The filesystem now handles creation of new files without write permission (for instance, cp -a needs this when copying a file which is readonly). Access to the filesystem can now be restricted to a group of processes (this is useful when running backups, to prevent locate indexing the backup fs). The sqlexport.py file which was missing in the last release is now included, so the sql-export command should work now.

  •  27 Nov 2012 00:08

Release Notes: This release improves the performance of the HashCache and reduces its memory usage. It adds an sql-export command to export file lists to PostgreSQL. It adds a find-missing command that shows filenames where file contents are unavailable. It adds a copy-expire command that copies expire tags from a remote repo.

  •  06 Sep 2012 01:14

Release Notes: This release reduces the memory required for bfsync clone/pull, improves the performance of different parts of bfsync and bfsyncfs, and fixes crash which could sometimes occur during bfsyncfs umount.

  •  18 Jul 2012 21:30

Release Notes: This release adds automated deletion of old versions via the new "expire" command. This is mainly intended for backups, and allows specifying how long to keep daily/weekly/monthly/yearly backups. It adds manual deletion of the old version via new "(un)delete-version" commands. Conversion of bfsync-0.3.1 to bfsync-0.3.2 repositories can be done using bfsync upgrade. Performance problems during pull/clone when applying diffs with many deletions have been fixed.

Screenshot

Project Spotlight

ECMA-55 Minimal BASIC

A minimal BASIC compiler.

Screenshot

Project Spotlight

XStow

A replacement of GNU Stow written in C++.