> So instead of keeping a centralized database and maintaining it, Fossil allows me to work on files and I don’t need to worry about hosting and upgrading a dat

> So instead of keeping a centralized database and maintaining it, Fossil allows me to work on files and I don’t need to worry about hosting and upgrading a database. I think I understand what you're saying. Compared to writing a Rails app and connecting it to a Postgres database, it's easier to dump files into a directory and push them to a Fossil server. Your wording is a bit confusing. Fossil is a database. Adding a file to the repo puts it in the database. fossil ticket add status 'open' comment 'Remember to buy a cat' type 'task' adds a record to the database. You can use the fossil sql command to query anything in the repo.