The new key is under pubkeys/heftig_nitrokey.pub, and pubkeys/heftig.pub
was renamed to pubkeys/heftig_yubikey.pub. Update root_ssh_keys to refer
to "heftig_nitrokey.pub" as "heftig.pub" does not exist anymore.
Fixes: 13a4bddf0d ("pubkeys/heftig: Add my new Nitrokey, reorganize")
With the final lists migrated to mailman3[1], the mailman2 server can
finally be killed.
When the mailman3 server was initially setup[2], it was done on a
separate server because the mailman and mailman3 packages conflicted,
and the traffic was routed over wireguard (HTTP, LMTP and SMTP).
Instead of installing mailman3 on the original lists.al.org server and
transferring the data, it was easier just to install the missing pieces
(basically Postfix and adjusting the Nginx configuration) on the ml3
server and move the IPs (to keep the IP mail reputation).
So basically the following was done:
- The IPs for the original lists.al.org was moved to the mailman3.al.org
server
- The mailman2 datadir was transferred to mailman3.al.org server, so we
can keep the pipermail links alive, and import missing mails if needed
- The original lists.al.org server was decommissioned
- The mailman3.al.org server was renamed to lists.al.org
- The missing pieces was added to the mailman3 role (basically Postfix +
Nginx adjustments)
- The mailman role was deleted and the mailman3 role renamed to mailman
[1] 75ac7d09 ("mailman: Fourth and final batch of mailman3 migrated lists")
[2] 9294828f ("Setup mailman3 server")
Fix #59
These are used to signal the start of the document in a stream of many
documents. As Ansible only supports one YAML document per file this is
unnecessary. About a third of our YAML documents already lacked these.
klausenbusk is our new newest Junior DevOp and he needs some access:
* bugs.al.org for helping with migrating Flyspray tasks to GitLab
* monitoring.al.org for setting up centralized logging
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.
Kristian Klausen
Christian Heusel
Jan Alexander Steffens (heftig)
Evangelos Foutras
Evangelos Foutras
Sven-Hendrik Haase
Jelle van der Waa
Giancarlo Razzolini
Jelle van der Waa
Florian Pritz