Hacker News Reader

My favourite thing about fossil is that the repo is a single SQLite database file so it’s extremely to just back it up or keep the repo in cloud storage. With Git I’ve always had problems with conflicts in the .git directory which messes things up, but fossil is a single file so it backs up to the cloud wonderfully.

View on HN

That's surprising. Doesn't it seem like one big file would increase the odds of a sync conflict?

for simgle users (hobby projects) that's not a concern. For teams, you'd go through a hosted server anyway.

Sure, but the original post said that it was a concern for Git but not for Fossil. I was wondering why that is.

There is an extensively tested sync protocol, the whole file does not get synced each time.

https://fossil-scm.org/home/doc/trunk/www/sync.wiki

I think the original comment was talking about a generic sync utility, not about Fossil's or Git's own protocols:

> so it’s extremely to just back it up or keep the repo in cloud storage

A single big file seems like it would cause more issues for a generic sync utility. Though I guess I can imagine sync algorithms that work better with one style vs the other.

Reply on news.ycombinator.com