We want to migrate to mailman3 as mailman2 is basically unmaintained and requires Python 2 which is EOL. Because the mailman and mailman3 packages conflict and we don't want to perform a big bang migration, mailman3 must be deployed on a separate server. mailman-web (mailman3's web interface) hasn't been packaged yet, so for now we are using my homebrewed PKGBUILD[1]. [1] https://gist.github.com/klausenbusk/5982063f95c503754a51ed2fefb8915e Ref #59
3.6 KiB
Servers
Table of contents
[[TOC]]
gemini
Services
- repos/sync (repos.archlinux.org)
- sources (sources.archlinux.org)
- archive (archive.archlinux.org)
lists.archlinux.org
Services
- mailman
archlinux.org
Services
- archweb (Arch's site)
aur.archlinux.org
Services
- aurweb
bugs.archlinux.org
Services
- flyspray
bbs.archlinux.org
Services
- bbs
phrik.archlinux.org
Services
- phrik (irc bot) users in the phrik group defined in the hosts vars and re-used the archusers role. Users in the phrik group are allowed to restar the irc bot.
state.archlinux.org
Services
- postgres server for terraform state
quassel.archlinux.org
Services
- quassel core
matrix.archlinux.org
Services
- Matrix homeserver (Synapse)
- Matrix ↔ IRC bridge
homedir.archlinux.org
Services
- ~/user/ webhost
accounts.archlinux.org
This server is special. It runs keycloak and is central to our unified Arch Linux account management world.
It has an Ansible playbook for the keycloak service but that only installs the package and starts it but it's configured via a secondary Terraform file only for keycloak keycloak.tf
.
The reason for doing it this way is that Terraform support for Keycloak is much superior and it's declarative too which is great for making sure that no old config remains in the case of config changes.
So to set up this server from scratch, run:
cd tf-stage1
terraform apply
cd ../tf-stage2
terraform import keycloak_realm.master master
terraform apply
Services
- keycloak
mirror.pkgbuild.com
Services
- Regular mirror.
reproducible.archlinux.org
Services
- Runs a master rebuilderd instance two workers:
- repro1.pkgbuild.com (packet.net Arch Linux box)
runner2.archlinux.org
Medium-fast-ish packet.net Arch Linux box.
Services
- GitLab runner
mail.archlinux.org
Services
- postfix (mail server)
- rspamd
- dovecot (imap)
monitoring.archlinux.org
Prometheus, Loki and Grafana server which collects performance/metrics and logs from our services and runs alertmanager.
Services
- Alertmanager
- Grafana and docs/grafana.md
- Prometheus
dashboards.archlinux.org
Prometheus, and Grafana server which receives selected performance/metrics from monitoring.archlinux.org and make them public accessible.
Services
- Grafana and docs/grafana.md
- Prometheus
patchwork.archlinux.org
Services
- patchwork
redirect.archlinux.org
Services
- Redirects (nginx redirects)
- Authoritative DNS server (PowerDNS) for ACME DNS challenges
- ping
security.archlinux.org
Services
- security tracker
wiki.archlinux.org
Services
- archwiki
md.archlinux.org
Online collborative markdwown editor for Arch Linux Staff.
mailman3.archlinux.org
This server runs mailman3 as mailman2 and mailman3 can't be installed on the same server. The HTTP and LMTP traffic is routed over WireGuard from lists.archlinux.org.
Services
- mailman3
Services
Archive Mirrors
The Arch Linux Archive is mirrored to three dedicated servers to help aid global availability.