Fossil is a simple, high-reliability, distributed software configuration management system with these advanced features:
Integrated Bug Tracking, Wiki, and Technotes - In addition to doing distributed version control like Git and Mercurial, Fossil also supports bug tracking, wiki, and technotes.
Built-in Web Interface - Fossil has a built-in and intuitive web interface with a rich variety of information pages (examples) promoting situational awareness.
This entire website is just a running instance of Fossil. The pages you see here are all wiki or embedded documentation or (in the case of the download page) unversioned files. When you clone Fossil from one of its self-hosting repositories, you get more than just source code - you get this entire website.
Self-Contained - Fossil is a single self-contained stand-alone executable. To install, simply download a precompiled binary for Linux, Mac, OpenBSD, or Windows and put it on your $PATH. Easy-to-compile source code is also available.
Simple Networking - No custom protocols or TCP ports. Fossil uses ordinary HTTP (or HTTPS or SSH) for network communications, so it works fine from behind restrictive firewalls, including proxies. The protocol is bandwidth efficient to the point that Fossil can be used comfortably over dial-up.
CGI/SCGI Enabled - No server is required, but if you want to set one up, Fossil supports four easy server configurations.
Autosync - Fossil supports "autosync" mode which helps to keep projects moving forward by reducing the amount of needless forking and merging often associated with distributed projects.
Robust & Reliable - Fossil stores content using an enduring file format in an SQLite database so that transactions are atomic even if interrupted by a power loss or system crash. Automatic self-checks verify that all aspects of the repository are consistent prior to each commit.
Free and Open-Source - Uses the 2-clause BSD license.
PC Game System Requirements, News And Hardware Test Tools
Hi,
I've talked about SSHFP in my last blog post and now, let’s talk about TLSA, another useful DNS record to put in a DNSSEC secured zone.
I will apply the example to HTTPS here but you can do this for everything that use TLS in fact (except for the web browser plugin part).
DANE and TLSA
Guetzli
Introduction
Guetzli is a JPEG encoder that aims for excellent compression density at high visual quality. Guetzli-generated images are typically 20-30% smaller than images of equivalent quality generated by libjpeg. Guetzli generates only sequential (nonprogressive) JPEGs due to faster decompression speeds they offer.
Add Brotli compression support to Apache for static assets and pages
The Apache web server doesn’t yet support stream compression using Brotli, but it’s easy to add support for static pages and assets such as CSS and Javascript files that you precompress. Browser support for Brotli is coming in Firefox 44 and in Chrome, and it provides about 15% savings versus precompressing with gzip/deflate.
First, download and build Brotli if it’s not already installed on your system. You’ll need to run make in the “dec”, “enc” and “tools” directories to build the bro executable. A quick note here, if you’re using an older version of GCC you might get an error message because your g++ doesn’t support the -std=c++11 flag. I ran into this on an older Debian server (GCC 4.6.3 from 2011), changed -std=c++11 to -std=c++0x in the CXXFLAGS line of shared.mk, and the build completed normally.
Compress and configure
Next, compress your files. If you already have static files compressed with the .gz extension, here’s a one-liner to recompress them all using bro: