1
1
mirror of https://gitlab.archlinux.org/archlinux/infrastructure.git synced 2026-03-01 21:26:25 +01:00
infrastructure/roles/archwiki
Kristian Klausen 0991324392
Switch to nginx native ACME[1] where it makes sense
It provides a better UX compared to certbot and is one less moving part.

The switch is done where it is possible and sensible. That is basically
all the places where nginx is the sole user of the certificate.

Certificates using the DNS-01 challenge (e.g. geo mirrors) or which are
used with stream (e.g. rsync over TLS) still require certbot as it is
currently not supported in the native integration[2][3].

[1] https://blog.nginx.org/blog/native-support-for-acme-protocol
[2] https://github.com/nginx/nginx-acme/issues/11
[3] https://github.com/nginx/nginx-acme/issues/13
2025-12-23 19:46:18 +01:00
..
defaults archwiki: Update to 1.45.1-1 2025-12-15 16:54:18 +01:00
files Add opt-in Anubis for the wiki to combat scraping 2025-08-09 17:50:22 +02:00
handlers archwiki: Add memcached@archwiki handler 2025-03-22 03:49:22 +01:00
meta Add opt-in Anubis for the wiki to combat scraping 2025-08-09 17:50:22 +02:00
tasks Switch to nginx native ACME[1] where it makes sense 2025-12-23 19:46:18 +01:00
templates Switch to nginx native ACME[1] where it makes sense 2025-12-23 19:46:18 +01:00