It turns out restic is a bit less trivial to set up with Amazon’s S3
due to some incoherency in URI handling by Amazon S3 leading to subtle
problems with repo initialization where restic init is only fine with
a specific variant of the S3 bucket URI and all other restic commands would
work with another one. While the linked bug is about Scaleway’s object storage,
the problem encountered also applied to AWS S3.
This post documents an Ansible sample variable setup to automatically generate proper restic repository paths.
I rarely complain on others’ software, but this time I felt compelled to share my first impression on GORM, since it’s quite an example of how you pick software you need.
Since you usually don’t care much about the upsides but rather have blockers preventing you from using something at all, let’s get right to the negative side.
The market of the software to replace GnuPG and the OpenPGP infrastructure appears to be quite a topic on itself, the precondition to replace GnuPG being its complexity (which has gone to levels so high the official library to interface with GnuPG, gpgme, is literally a command-line wrapper1 to GnuPG), it being the de-facto implementation of OpenPGP, and its other problems, as commonly illustrated by this post by Latacora.
You can read the Russian version of this post here.
Restic, the simple backup program, is a fairly well-known piece of software. Designed to be simple to both use and script on any system, it doesn’t include any OS-specific setup examples, which is precisely what this post describes.
So what we’re trying to achieve here:
psql -f.