I use Fossil to store my collection of presentations (a big pile of *.odp files averaging 5MB each). And that works. But storing thousands and thousands of MP4 files totally 70GB is a little over the top. I think this is out-of-band for what Fossil is designed to do.
On Thu, May 23, 2013 at 7:56 AM, Kumar <[email protected]> wrote: > Hi all, > > Anyone here using fossil to manage your iTunes collection? > > Recently I decided to step away from relying on Time Machine (on MacOSX) > for backing up my iTunes collection of about 70GB. I want my collection to > be stored on two hard disks in sync and with complete history. > > I use fossil for my personal projects by default, so that first thing that > occurred to me was to bundle it into a fossil repo and put it on one hard > disk and put a checkout on another. > > That didn't work, since my files exceed the max blob size that fossil can > store. I'm currently using git, which works fine with these files. > > Should I even be expecting this to work? The nice bit about the fossil > file is that periodically, I can just hand it over to Amazon deep freeze > cold storage, whereas with git I would need an additional packaging step. > > Thoughts? Am I crazy? > -Kumar > > > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > -- D. Richard Hipp [email protected]
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
