Skip to content
Snippets Groups Projects
  1. Aug 17, 2024
  2. Jul 11, 2024
  3. Jun 30, 2024
  4. Jun 14, 2024
  5. Jun 08, 2024
  6. May 11, 2024
  7. May 03, 2024
  8. Feb 10, 2024
  9. Jan 19, 2024
  10. Dec 31, 2023
  11. Dec 09, 2023
  12. Nov 22, 2023
  13. Oct 15, 2023
  14. Aug 19, 2023
    • Kristian Klausen's avatar
      Create sandbox DNS zone · b2ffb068
      Kristian Klausen authored
      The VMs created in the Hetzner cloud sandbox project must be accessible
      with a DNS name. This creates a dedicated DNS zone for this purpose.
      
      For now this zone will only be used by the aurweb project, so it can
      create DNS records for the VMs it creates. This is needed so the dynamic
      created environment can be accessed over HTTPS.
      
      [1] https://docs.gitlab.com/ee/ci/review_apps/
      Verified
      b2ffb068
  15. Aug 13, 2023
  16. Aug 06, 2023
  17. Jul 10, 2023
  18. Jun 29, 2023
    • Giancarlo Razzolini's avatar
      Redirect status to the non CNAME version for now · dbaee79e
      Giancarlo Razzolini authored
      Until we get our situation with uptimerobot fixed, we are redirecting
      status.archlinux.org to the standard uptimerobot URL, that is provided
      with their free plan. Once/if we re-gain our premium access, we can
      simply revert this MR.
      dbaee79e
  19. Jun 22, 2023
  20. May 28, 2023
  21. May 24, 2023
  22. May 07, 2023
  23. May 06, 2023
  24. Apr 02, 2023
  25. Mar 03, 2023
  26. Feb 24, 2023
  27. Feb 21, 2023
  28. Feb 11, 2023
  29. Jan 28, 2023
  30. Jan 12, 2023
  31. Jan 08, 2023
  32. Jan 05, 2023
  33. Nov 17, 2022
  34. Oct 29, 2022
  35. Sep 28, 2022
    • Kristian Klausen's avatar
      Kill the mailman2 server and put the mailman3 server in its place · 893a95f3
      Kristian Klausen authored
      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
      Verified
      893a95f3
  36. Sep 16, 2022
Loading