1
1
mirror of https://gitlab.archlinux.org/archlinux/infrastructure.git synced 2024-09-20 11:54:39 +02:00
Official Arch Linux Infrastructure Repository
Go to file
2017-11-26 16:18:02 +01:00
group_vars postfix: Fix certificate domain name for non-primary mail servers 2017-11-18 16:18:56 +01:00
host_vars postfix: Fix certificate domain name for non-primary mail servers 2017-11-18 16:18:56 +01:00
library dbscripts: Add module for staging directory creation 2017-01-29 18:59:58 +01:00
misc Give Jelle root permissions 2017-06-12 10:43:44 +02:00
playbooks Deploy basic config on nymeria and dragon 2017-11-20 21:32:02 +01:00
pubkeys pubkeys: Update jelle's key 2017-11-19 16:49:18 +01:00
roles gitpkg: Make default meson funcs a bit more compact 2017-11-26 16:18:02 +01:00
.gitignore Initial config check-in for vostok and orion 2016-05-17 13:32:05 +02:00
.gitmodules common: Add checkservices script 2016-08-01 16:09:51 +02:00
ansible.cfg ansible.cfg: Enable the profile_tasks callback plugin 2017-08-22 17:49:44 -03:00
hosts root_ssh: Add dragon's key to nymeria/luna 2017-11-25 10:37:09 +01:00
README.md Update README regarding installation and certbot 2017-11-06 09:52:22 +01:00

Arch Infrastructure

This repository contains the complete collection of ansible playbooks and roles for the Arch Linux infrastructure.

It also contains git submodules so you have to run git submodule update --init --recursive after cloning or some tasks will fail to run.

Instructions

All systems are set up the same way. For the first time setup in the Hetzner rescue system, run the provisioning script: ansible-playbook playbooks/install-arch.yml -l $host. The provisioning script configures a sane basic systemd with sshd. By design, it is NOT idempotent. After the provisioning script has run, it is safe to reboot.

Once in the new system, run the regular playbook: ansible-playbook playbooks/$hostname.yml. This playbook is the one regularily used for adminstrating the server and is entirely idempotent.

Note about first time certificates

The first time a certificate is issued, you'll have to do this manually by yourself. First, configure the DNS to point to the new server and then run a playbook onto the server which includes the nginx role. Then on the server, it is necessary to run the following once:

certbot certonly --email webmaster@archlinux.org --agree-tos --rsa-key-size 4096 --renew-by-default --webroot -w /var/lib/letsencrypt/ -d <domain-name>

Note that some roles already run this automatically.

Note about opendkim

The opendkim DNS data has to be added to DNS manually. The roles verifies that the DNS is correct before starting opendkim.

The file that has to be added to the zone is /etc/opendkim/private/$selector.txt.

Servers

vostok

Services

  • backups

orion

Services

  • repos/sync (repos.archlinux.org)
  • sources (sources.archlinux.org)
  • archive (archive.archlinux.org)

apollo

Services

  • bbs (bbs.archlinux.org)
  • wiki (wiki.archlinux.org)
  • aur (aur.archlinux.org)
  • mailman
  • planet (planet.archlinux.org)
  • bugs (bugs.archlinux.org)
  • archweb
  • patchwork
  • projects (projects.archlinux.org)

soyuz

Services

  • build server (pkgbuild.com)
  • releng
  • torrent tracker
  • sogrep
  • /~user/ webhost
  • irc bot (phrik)
  • quassel core