I needed a local mercurial hosting option. The following is what I came up with. Hopefully, you will find it useful or the post at least gives you some ideas. My requirements were basic. Web browsable repositories Minimal and maintenance-free Support for pushing new changesets Accessible through a URL to easily pull dependencies Needed access from a single computer (which let me omit authentication) I didn’t need bug tracking, code review, or anything fancy.
SpamAssassin won’t do much if it hasn’t been trained. While it does come with a few plugins enabled for DKIM, SPF, RBL, and content checks, SpamAssassin is limited unless you train its Bayesian filter. The Bayesian filter will compare past content from known spam and ham emails to determine the likelihood of spam. Bayes' theorem, named after 18th-century British mathematician Thomas Bayes, is a mathematical formula for determining conditional probability.
Are you curious about SpamAssasin’s sa-update tool and what it does? As with many other programs geared towards servers, there are additional tools that are run inside of cron jobs and used by administrators. Knowing what these tools do and how they work can help you better understand your server and fix issues down the line. The sa-update tool is used to pull new configuration files and rules from channels. These new files are used by SpamAssassin to classify emails as spam in addition to the Naive Bayes filtering.
On the surface QCAD and LibreCAD and every other 2D CAD software is the same, offering the same basic tools, user interface, and supported file formats. The small differences will either have you praising the software developers or cursing them as you spend your precious time fiddling with the quirks. In 2011 LibreCAD was forked from QCAD version 2. In the software development community, forking is the process of duplicating a project and having it be developed by a different group of engineers.
When managing any type of server, it’s generally wise to have a solution in place for when a server fails or when the server needs to be taken offline. When working on a high availability server setup, the question is how to quickly transfer activity from the failed or offline server to the backup server. One method is to use IP failover, which is the focus of this post. In short, IP failover is the method of moving the IP address of the failed server to the backup server, allowing requests to be handled by the backup server until the main server is once again functional.