‹ jan0sch.de

Tags / Software

Recently I got inspired to try out the December Adventure and so here we are.

It has been nearly two years now since I switched from Sylpheed to aerc as my daily driver for email.

While Sylpheed still is an awesome email client my switch was triggered by more heavy usage of a laptop than before and the discovery of usability problems I thought long solved like:

  • very high resolution but applications either zoomed / scaled which results in less space than needed
  • unwieldy mouse handling (touch pads suck)
  • after disabling application zooming fonts and icons were barely readable

The default expectation of the wonderful aerc email client is the usage of abook as address book. Also most people seem to use calcurse for calendars. However what if we want to switch?

Some of us prefer to use console (text terminal) tools for productivity and that is just fine. In this tutorial we’ll explore how to synchronise address books and calendars via the DAV protocols for the khard address book and the khal calendar.

The trouble started when emails were coming in claiming first “Fail” and later “DegradedArray” events of a software raid running on a Debian Linux server. Looking into logs revealed an SSD (NVMe) died but let us look at it step by step.

Because setting an environment variable via a shell init file doesn’t seem to be en vouge in modern linux distributions we need to find other ways. To spare you breaking precious hardware in the process here is the solution:

You can define “.conf” files within the directory ~/.config/environment.d/ that may contain one variable definition per line and out of these the startup environment for your window manager will be constructed.

With the release of version 1.9.0 sbt is deprecating the IntegrationTest configuration. Read on to learn how to migrate to tagged tests instead.

While the recommended migration path is to create a subproject in which you pool all your integration tests, I respectfully disagree and suggest to use tagging to filter tests during test runs.

For quite a long time PostgreSQL supports authentication via SCRAM-SHA-256 now, so migrating is long overdue. This small guide will show you how to do this.

The support for SCRAM-SHA-256 was introduced in version 10 of the PostgreSQL database and it is the default for freshly installed systems since version 13.

Since it is not only used for internal storage of password hashes on the database side but also for clients which have to hash their connection password in the correct way there likely was some impact when databases were upgraded. However in some cases clients were not ready and so sometimes the DBMS was configured to stick with md5 and most likely forgotten. ;-)

Without further configuration you will not be able to put a widget from TeamCity onto a dashboard in Hub. Usually you can create a widget but it will not load any data complaining about “Cannot load project list” or something similar.

The reason for it is that some CORS configuration on the TeamCity side is needed.

VCS usually have hooks into which commands can be “plugged” to be executed automatically upon certain events and the great darcs is no exception.

Having your code checked for formatting guidelines before you record (commit) it is quite convenient and so let us implement a prerecord hook for darcs that instruments sbt to check you code style.

There are scenarios when you might want to automatically create snapshots via ZFS to have a backup ready if needed. The features of ZFS make this straightforward and easy. However this also means that you might run into trouble because of having too many snapshots.

« ältere Beiträge neuere Beiträge »