{"id":166585,"date":"2026-03-27T23:12:55","date_gmt":"2026-03-27T21:12:55","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/fossil-scm-2-28"},"modified":"2026-03-27T23:12:55","modified_gmt":"2026-03-27T21:12:55","slug":"fossil-scm-2-28","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/fossil-scm-2-28","title":{"rendered":"Fossil SCM 2.28","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

<\/p>\n

After five and a half months of development, the release of 2.28 of the simple and highly reliable distributed cross-platform system took place. configuration management<\/a> Fossil SCM<\/a>, developed by the author of SQLite, Dwayne Richard Hipp<\/a>.<\/p>\n

<\/noindex><\/p>\n

Fossil SCM stands out among version control systems for its radical simplicity of deployment: the entire project is a single executable file without external dependencies, which simultaneously serves as a VCS, embedded web server, bug tracker, wiki, forum, and chat. The entire repository, along with all history, tickets, and wiki, is stored in a single SQLite file \u2014 it can be copied, backed up, or sent to a colleague with a single scp command. The project is used by its creator for the development of SQLite \u2014 which in itself speaks to the reliability of the tool. Unlike Git, Fossil was originally designed with a focus on data integrity and ease of self-hosting: setting up your own server is literally just one command fossil server. The philosophy of the project is that 'everything necessary for the life of the project is in one place', without external services and complex infrastructure.<\/p>\n

<\/noindex> In the new version:<\/p>\n