Fix #354

Sven-Hendrik Haase authored 3 years ago and Kristian Klausen committed 3 years ago

Co-authored-by: Kristian Klausen <kristian@klausen.dk>

The TU Bylaws is currently deployed as part of the aurweb role which
makes it more work for devops and with gitlab pages TU's can deploy it
themself.

The WKD setup for master-key.archlinux.org requires this domain to
obtain the master keys via WKD. As WKD falls back to archlinux.org which
contains no .well-known/openpgpkey entry.

Eg. https://whatcanidoforfedora.org/ and
https://whatcanidoformozilla.org/. Mea culpa.

Loki keeps logs it returns in ram, resulting in the oom killer on 2GB's
of ram.

Fix #303

[1] https://gitlab.archlinux.org/archlinux/archlinux-bugs-snapshotter

This allows us to get proper certificates for loki which will run on logging.archlinux.org
on the same machine as monitoring.archlinux.org.

It was getting very cramped with only a few MBs left. It appears currently we only get about 6 months worth of data out of 20G
so 100G seems reasonable.

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

This adds a collaborative markdown editor as newly offered service which
is available via login for all Arch Linux Staff with an option to allow
anonymous edits by users (not default). Users are managed via keycloak
and require the Staff role to be allowed in, non staff keycloak users
currently will receive an internal server error due to an upstream
issue.

machine.domain has been an mandatory attribute which creates
<domain>.archlinux.org entries automagically. For migrations this can be
a problem if <domain>.archlinux.org supposed to point to a different
machine. Adding the new machine with the same domain leads to additional
DNS entries. The DNS ends up pointing to both machines in this case.
By making the domain attribute optional for machines, we allow the new
machines to be created without any domain pointing to them.

The ttl must be aligned with the previous entries.

Lowered the CNAME DNS record TTL for lists to 600 and created a new cx11 server
to migrate lists.archlinux.org to.

The WKD will be migrated to Gitlab Pages, requiring a lowering of DNS
TTL.

Kristian Klausen authored 4 years ago and Frederik Schwan committed 4 years ago

We need to keep the balance between automation and readability.

luna uses the luna domainkey now, instaed of the luna2 domainkey. The
list (hosted on luna) also use lists.archlinux.org for all ml now[1].

[1] https://lists.archlinux.org/pipermail/arch-dev-public/2020-December/030248.html

Removed the A/AAAA entries for apollo, as well as any CNAME's pointing to it. Also
removed the domain key for apollo.

Pointed the mailman CNAME to the new redirect machine for finishing the apollo migration.