Fossil SCM 2.24 💾

Fossil is a distributed version control system, quite robust and easy to use. It manages local and remote repositories, user permissions, has a built-in wiki, bugtracker, release blog and an extendable web interface. It's github-in-a-box as all features are packed into a stand-alone executable which also doubles as server. Internally the database utilizes SQLite and allows extending that or its user interface through TCL or the builtin TH1 scripting language. An optional JSON API permits further

minor feature: Apache change work-around As part of a security, the Apache webserver Mod_cgi module has stopped relaying the Content-Length field of the HTTP Reply header from the CGI programs back to the client in cases where the Connection is to be and the client is able to read until end-of-file. The HTTP and CGI specs allow for this, though it does seem rude. Older versions of Fossil were depending on the Content-Length header field. Being set. To work around the change to Apache, Fossil has Been enhanced to cope with a missing Content-Length in the reply header. See Forum thread 12ac403fd29cfc89. Skin enhancements: Reworked the default skin to make everything more readable: larger. Fonts, more whitespace, deeper indents to show hierarchy and to Offset command examples, etc. Adjusted colors slightly to bring Things into better accord with the WCAG accessibility guidelines. This constitutes a. breaking change for those with. Custom skins; see this section of The docs for migration advice. Add a new link added to the /login page that allows the user to. Select their preferred skin. This preference is stored in The fossil display_settings cookie. The /setup_skin_admin page is simplified to let administrators easily. Select one of the built-in skins as a default, or to specify a Custom skin. Reworked the default skin to make everything more readable: larger. Fonts, more whitespace, deeper indents to show hierarchy and to Offset command examples, etc. Adjusted colors slightly to bring Things into better accord with the WCAG accessibility guidelines. This constitutes a. breaking change for those with. Custom skins; see this section of The docs for migration advice. Add a new link added to the /login page that allows the user to. Select their preferred skin. This preference is stored in The fossil display_settings cookie. The /setup_skin_admin page is simplified to let administrators easily. Select one of the built-in skins as a default, or to specify a Custom skin. I

BSDL-2 c sqlite fossil scm dvcs wiki bugtracker server project-management cgi wcms