Currently our textcollector can sometimes fail with 'Failed to
create/acquire the lock /home/backup/$server/lock.exclusive (timeout)."
Instead of checking on a borg lock file, check if our backup snapshot
dir exists which the backup script creates and removes. This should give
less false positives then our current method.

Cache urls which urls marks as can be cached by nginx. This offloads our
uwsgi workers and allows for speedier delivery of RSS feeds and other
cached routes.

Due to users misconfiguring their conky to query for rss updates every
second add proper rate limitting to all rss endpoints in nginx.

The websocket support always 400'd as upgrade headers where missing for
/socket.io

Our dedicated servers are fairly slow when rebooting and are then not
available for 5 minutes, which means a ServiceDown notification is send
for a normal reboot.

More and more browsers and password managers support this[2].

[1] https://w3c.github.io/webappsec-change-password-url/
[2] https://github.com/w3c/webappsec-change-password-url/issues/16

Export the repository size of our repositories so they can be monitored
and we have some useful data for repository growth in the future.

The value of the expr is not really useful as of now, but if we show the
value of probe_ssl_earliest_cert_expiry it should show the date when the
cert expires.

Prometheus alerts $value is the result of the expression, so it will be
the amount of seconds since the last backup and not the last backup
date.

[1] https://lists.archlinux.org/pipermail/arch-dev-public/2021-January/030284.html

gemini takes a long time to run backups and it would sometimes produce false positives for not having backed up for some time.
The higher threshold should help with those false positives.

This service only requires MySQL access and ability to submit an email.

This service only requires MySQL access and access to the aur home
directory (/srv/http/aurweb) to write the package/pkgbase/user files.

This service only requires MySQL access, network connection access and
the ability to create an pyalpm handle to sync the pacman db's to update
the blacklist.

This service only requires MySQL access for deleting old, empty reserved
aurweb pkgbases.

This service only requires MySQL access for updating the per-package
popularity counts.

Should protect the filesystem from the script going amok and nuking the
filesystem (shouldn't happen).

Fix #272

Without a location block, nginx always executes the return block causing
a 302 which makes certbot unable to renew as it follows redirects.

The file should not be on the main domain as it adds unnecessary
complexity to the archweb role and there is a bigger chance that we
unintentionally break connectivity checking (which has happened in the
past[1][2]).

This doesn't remove the file from the main domain[3], as we need to ship
a updated NetworkManager package first.

[1] https://www.reddit.com/r/archlinux/comments/keai0g/does_anyone_know_if_this_is_normal/
[2] https://www.reddit.com/r/gnome/comments/ke9ytm/network_manager_popup/
[3] http://www.archlinux.org/check_network_status.txt

Fix #239

As mediawiki does not support PHP 8 yet in the current LTS release, we
have to stay with PHP 7.

The mirrors.kernel.org mirror seems to have network issues for us from
aur.archlinux.org which makes the aurweb-aurblup service fail from time
to time. Switch to our own mirror as we are in control.

Update fluxbb to the latest commit with PHP 8 compatibility, fix
permissions being to strict so http can't access it and rate limit
searching.

As reported in FS#69614 the lock should be before the delete for when
another sync job is running rsync can't move the files as they are
removed.

A lot of our systems have a "hardware" watchdog (ex: all the Hetzner
cloud servers) so let's use it.

Prefer using lists of maps with consistent keys.

yaml: truthy value should be one of [false, true] (truthy)
yaml: wrong indentation: expected 4 but found 2 (indentation)
yaml: too few spaces before comment (comments)
yaml: missing starting space in comment (comments)
yaml: too many blank lines (1 > 0) (empty-lines)
yaml: too many spaces after colon (colons)
yaml: comment not indented like content (comments-indentation)
yaml: no new line character at the end of file (new-line-at-end-of-file)
load-failure: Failed to load or parse file
parser-error: couldn't resolve module/action 'hosts'. This often indicates a misspelling, missing collection, or incorrect module path.