This never really worked to well and since basically all PIA boxes that we
balanced to have died by now and it's also pretty slow.

The magnet uri's and torrent files no longer include a torrent tracker
link so running the service is obsolete.

This PIA box was never btrfs, so do not set it as such as it will enable
the btrfs scrub timer.

As of now we don't use interactive web terminals, the open ports are
removed on all runners manually.

https://docs.gitlab.com/ee/administration/integration/terminal.html#security

As repro3 is Ubuntu and it's default shell is dash, set -o pipefail is
not supported.

It isn't used and Postfix was never configured to use it.

Added a new server for the mail migration.

Add federation_reader as a another worker.

Both boxes died and are no longer responsive, retire them.

Added the missing msa_header_checks to that tasks.

This also deprecates the somehwat disconnected docs github-mirror.md and new-gitlab.project.md

The fingerprints for the RSA and ECDSA key were swapped, fixed them.

It was Debian previously.

AURweb's rendercomment script uses python's libgit2 bindings which error
out when it can't read /home/aur/.git due to ProtectHome=true, instead
use ProtectHome=tmpfs.

This runner, as opposed to secure-runner1.archlinux.org, doesn't have any virtual machine capabilities and should be preferred for projects that don't need such capabilities.

We were seeing load spikes that pegged the server at 200% before.

This will ensure a smaller base image.

Apparently before if we ran a packer build to generate the arch base image, the problem was that it wouldn't pick up the fact that the machine was an hcloud server as that would only be checked after the first boot due to an ordering issue.
Now we manually make sure that packer builds (which are always on hcloud anyway) will always have the hcloud-init files installed properly.

Added the new ssh host keys fingerprints to the config.

After some consideration, we are going to start with a smaller server size
for the AUR and increase if necessary.

Since the AUR is high email traffic, apply the same rule as for luna,
and add the sasl_username for aur to the no limits list.